lhotari commented on code in PR #23583: URL: https://github.com/apache/pulsar/pull/23583#discussion_r1840292483
########## pip/pip-392.md: ########## @@ -0,0 +1,94 @@ +# PIP-392: Add configuration to enable consistent hashing to select active consumer for partitioned topic + +# Background knowledge + +After [#19502](https://github.com/apache/pulsar/pull/19502) will use consistent hashing to select active consumer for non-partitioned topic + +# Motivation + +Currently, for partitioned topics, the active consumer is selected using the formula [partitionedIndex % consumerSize](https://github.com/apache/pulsar/blob/137df29f85798b00de75460a1acb91c7bc25453f/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/AbstractDispatcherSingleActiveConsumer.java#L129-L130). +This method can lead to uneven distribution of active consumers. + +Consider a scenario with 100 topics named `public/default/topic-{0~100}`, each having `one partition`. +If 10 consumers are created using a `regex` subscription with the `Failover type`, all topic will be assigned to the same consumer(the first connected consumer). This results in an imbalanced distribution of consumers. + +# Goals + +## In Scope +- Address the issue of imbalance for `failover` subscription type consumers in single-partition or few-partition topics. Review Comment: > Here's my conclusion: **Pulsar current cannot avoid duplicate messages on the client side during broker or active consumer transfer scenarios, and this PIP doesn't introduce new issues because both consistent hashing and modulo algorithms will cause active consumer transfer.** The way how this PR introduces more frequent problems is that the consumer will switch frequently when new consumers get added. A rolling restart is a common problematic case. This is why the PIP document should at least document that this is a known problem and consequence of this change. I hope that @codelipenghui and @merlimat could share their view on this matter. -- 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]
