You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The drain.sh cannot correctly detect the type of queue in an address of both multicast and anycast routing types.
It treated a queue on that address as a temp queue which result in the message count of that queue being ignored.
To Reproduce
Steps to reproduce the behavior:
Deploy a broker with n replicas (n > 2)
create an address newaddress of both routingTypes on last pod
sending 100k messages to last broker pod on newaddress
scaledown to (n-1) replicas
during scaledown, observe the scaledown pod log, and it will logs that newaddress queue is a temp queue. The total message count to be scaledown is 0. This can prevent further retries and return successful even there are messages not migrated.
Platform (please complete the following information):
OS: [e.g. Fedora]
Version [e.g. 32]
CEKit version [e.g. 3.5.0]
Container build tool [e.g. podman]
Expected behavior
Optional, use if not obvious. A clear and concise description of what you expected to happen.
Screenshots
Optional, add screenshots to help explain your problem.
Additional context
Optional. Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
The drain.sh cannot correctly detect the type of queue in an address of both multicast and anycast routing types.
It treated a queue on that address as a temp queue which result in the message count of that queue being ignored.
To Reproduce
Steps to reproduce the behavior:
Platform (please complete the following information):
Expected behavior
Optional, use if not obvious. A clear and concise description of what you expected to happen.
Screenshots
Optional, add screenshots to help explain your problem.
Additional context
Optional. Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: