GitHub user lhotari edited a comment on the discussion: Key_Shared subscription with autoscaling enabled
Which Pulsar version are you using? In Pulsar 4.0+, [PIP-379](https://github.com/apache/pulsar/blob/master/pip/pip-379.md) minimizes the problem that you are describing. The PIP-379 implementation is enabled by default. (In some server configurations, it might be disabled, so you should ensure that `subscriptionKeySharedUseClassicPersistentImplementation` is set to use the default value `false`). PIP-379 related documentation: https://pulsar.apache.org/docs/4.1.x/concepts-messaging/#preserving-order-of-message-delivery-by-key Announcement in Pulsar 4.0 blog post: https://pulsar.apache.org/blog/2024/10/24/announcing-apache-pulsar-4-0/#enhanced-key_shared-subscription-scale-without-compromising-message-order GitHub link: https://github.com/apache/pulsar/discussions/25288#discussioncomment-16008283 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
