You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/01/27 15:52:45 UTC

[GitHub] JevonQ opened a new issue #3454: [Feature Request] Dynamically refresh client after updating the number of partitions when the routing mode is not key hash

JevonQ opened a new issue #3454: [Feature Request] Dynamically refresh client after updating the number of partitions when the routing mode is not key hash
URL: https://github.com/apache/pulsar/issues/3454
 
 
   According to the web page (admin-api-partitioned-topics, https://pulsar.apache.org/docs/en/admin-api-partitioned-topics/), when admin increases the number of partitions on an existing partitioned topic, the newly created partition will not be seen until the producers/consumers are recreated. I think the way is not friendly for the users.
   
   I understand that the requirement is needed for key hash routing mode because increasing/decreasing the partition number can violate partition ordering. But I don't think it is mandatory for round-robin/single default mode. So I'm proposing to recreate producers/consumers within the pulsar client and make the whole process invisible to the application when the admin changes the partition number when the routing mode is not key hash.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services