Loading...

XML

Word

Printable

Type: Story
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: AMQ 7.8.2.GA
Component/s: container image, high-availability
Labels:
- drainer

Epic Link:
Message Migration
Blocked:
False
Ready:
False
GSS Priority:
Target Release:

AMQ 8.0.0.OPR.1.GA

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

When we scale down, and the remaining broker hits the following bug ~~ENTMQBR-5233~~ (Scale down would fail if target queue's id greater than max int). The drainer must catch those errors and not show the following line: "AMQ221078: Scaled down xxxx messages total" since those messages are LOST.

The drainer MUST care and guarantee that those messages are received by the remaining broker.

is related to

ENTMQBR-8106 AMQ Broker Drainer pod doesn't function properly after changing MessageMigration in CR

Backlog

ENTMQBR-5233 Scale down would fail if target queue's id greater than max int

Closed

ENTMQBR-8530 [Docs] AMQ Broker Drainer pod doesn't function properly after changing MessageMigration in CR

Closed

ENTMQBR-8112 Drainer pod reports success despite failing to resolve the broker URL & failure to migrate

Closed

relates to

ENTMQBR-6414 Drainer task should be run as a job and not as unmanaged pod

To Do

ENTMQBR-8610 [Docs] Drainer task should be run as a job and not as unmanaged pod

Closed

(1 relates to)

Assignee:: Unassigned

Reporter:: Abel Bouchama

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2021/09/09 7:57 AM

Updated:: 2024/04/22 12:18 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates