RahimovIR opened a new issue #7864:
URL: https://github.com/apache/pulsar/issues/7864
**Describe the bug**
In failover mode, the broker selects the master consumer based on
connection order, not priority level and not the lexicographical sorting of a
consumer name.
**To Reproduce**
Steps to reproduce the behavior:
1. Subscribe consumer1 with name "bbb" and PriorityLevel 1
2. Subscribe consumer2 with name "aaa" and PriorityLevel 0
3. See subscribe log:
[21:56:44.483 INF 9] consumer(1, bbb, -1) starting subscribe to topic
persistent://public/default/topic-a
[21:56:44.519 INF 5] consumer(1, bbb, -1) subscribed to topic
persistent://public/default/topic-a
[21:56:44.531 INF 5] consumer(2, aaa, -1) starting subscribe to topic
persistent://public/default/topic-a
[21:56:44.570 INF 7] consumer(2, aaa, -1) subscribed to topic
persistent://public/default/topic-a
[21:56:44.578 INF 7] consumer(2, aaa, -1) ActiveConsumerChanged
isActive=False
[21:56:45.518 INF 6] consumer(2, aaa, -1) ActiveConsumerChanged
isActive=False
[21:56:45.517 INF 7] consumer(1, bbb, -1) ActiveConsumerChanged isActive=True
**Expected behavior**
Active consumer must be consumer1 with name "aaa", but set consumer2 with
name "bbb"
The same behavior is observed if the PriorityLevel of both consumer is set 0
**Desktop (please complete the following information):**
- Broker run in docker apachepulsar/pulsar:2.6.0
- Client: pulsar-client-dotnet on windows
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
