zbentley commented on issue #15705: URL: https://github.com/apache/pulsar/issues/15705#issuecomment-1133918270
@codelipenghui if I'm reading that correctly, that's really concerning behavior. If a topic has no consumers, and a backlog of message index:key pairs `0:a, 1:a, 2:a, 3:b, 4:b, 5:b`, and a KeyShared consumer `c1` joins with a receiver queue size of 1 and gets message 0, why would we prevent a new consumer `c2` from joining and getting messages 3-5? That doesn't compromise key ordering in any way. Am I interpreting it correctly that: a new key shared consumer that connects to the topic when the newest message has position `X` will not receive **any** messages until the oldest unacked message in the subscription is newer than or equal to `X`? If that's the current behavior, it should be really prominently documented (potentially in a warning/highlighted way). -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
