szkoludasebastian commented on issue #22709: URL: https://github.com/apache/pulsar/issues/22709#issuecomment-2112363505
> > So we are using `Key_Shared` subscription. > > This isn't really about this bug, but since it came up, I'll comment about this. > > Is there a specific reason to use `Key_Shared` together with partitioned topics? Since you already have a 100 partitions, I'd assume that a better solution would be to use `Failover` subscription type. In general, `Key_Shared` is recommended when you have one or few topics and would like to scale key-ordered processing by adding more consumers. The docs aren't very clear about this recommendation. There's some explanation in https://pulsar.apache.org/docs/3.2.x/concepts-messaging/#failover--partitioned-topics . In Pulsar 3.0.0 improvements were made in this area with PR #19502 . We are using `Key_Shared` subscription because we need to be sure that messages with same key are coming to same consumer. We have our own custom deduplication mechanism which is based on local cache map so we need to have messages with same key in the same consumer -- 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]
