codelipenghui commented on issue #9585:
URL: https://github.com/apache/pulsar/issues/9585#issuecomment-782479524


   > When the topic is deleted forcefully with auto-creation, it recreates 
regular topics with the same names as the deleted partitions and not as 
partitioned topic. Also it does not subscribe to these topics. Is it correct 
doing so ? Naively, I would suggest that it must recreate a partitioned topic 
as it was.
   
   Yes, the current behavior is recreating "partitions" since the consumer 
already subscribed to each partition. For the partitioned topic, the consumer 
fetches the partitioned metadata first then subscribes to each partition. Do 
you mean the partitions are created but the consumer does not subscribe to 
them? This is not expected behavior. If you want to recreate a partitioned 
topic you can change the topic auto-create mode to 'partitioned' in the 
broker.conf `allowAutoTopicCreationType`.
   
   >  it detects that and ignores it with error message (See 
MultiTopicsConsumerImpl.subscribeIncreasedTopicPartitions). It treats only the 
case of increasing partitions as the method name suggests.
   
   This handles the partitions scaling. This will not affect the reconnect 
behavior. Essentially, the re-subscribe is processed in each consumer(under 
multi-topic 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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to