zbentley commented on issue #15705: URL: https://github.com/apache/pulsar/issues/15705#issuecomment-1137465277
@merlimat that's not accurate; if I start a KeyShared consumer `c1` per the test setup here, wait until it receives its first message, then start another consumer `c2`, then trigger `c1` to nack all of its messages, then `c2` starts getting (some, not all, hash-based) messages. Is that not supposed to happen? [The docs](tests/unit/test_checksum.py) seem to indicate that this is expected: > Be aware that negative acknowledgments on ordered subscription types, such as Exclusive, Failover and Key_Shared, might cause failed messages being sent to consumers out of the original order. Additionally, how does [allowOutOfOrderDelivery](https://pulsar.apache.org/api/client/2.6.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.html#allowOutOfOrderDelivery) work with the Python/C++ client? Is that on by default? Off by default? Lastly, how does the setting that @xuesongxs mentioned (`subscriptionKeySharedUseConsistentHashing`) affect this behavior? I thought that setting only affected what keys new consumers assume ownership from when they arrive; does it also affect how those consumers get messages (nacked or backlogged) that were already in the topic when they joined? -- 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]
