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 2022/02/25 07:36:43 UTC

[GitHub] [pulsar] michaeljmarshall edited a comment on issue #14438: sometimes internalDeleteTopicForcefully will block forever

michaeljmarshall edited a comment on issue #14438:
URL: https://github.com/apache/pulsar/issues/14438#issuecomment-1050576074


   Based on that thread dump, it looks like the blocking is coming from this code:
   
   https://github.com/apache/pulsar/blob/0ef7baa5131f0dee4a57e61eae1d7686f7f60f1e/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java#L2279-L2284
   
   When the zk thread completes the future returned by `fetchPartitionedTopicMetadataAsync`, it completes the callback on the `metadata-store` thread. That callback is then going to lead to a call to metadata store, which needs to run the callback on the `metadata-store` thread, but that thread is already in use.
   
   The fundamental issue here is deadlock.
   
   @merlimat @lhotari @codelipenghui @eolivelli - I think we should seriously consider solving this deadlock scenario for 2.10.0.
   
   EDIT: added reference to 2.10.0


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org