lhotari commented on pull request #13124:
URL: https://github.com/apache/pulsar/pull/13124#issuecomment-985602309


   > Recent deadlock cases happened on this single thread exectutor 
`org.apache.pulsar.metadata.impl.AbstractMetadataStore#executor`. And in 
current implementation, all metadata callbacks run on this executor. In my 
understanding, it won't cause zk session expiration.
   
   @Jason918 Can you provide examples of recent deadlock cases? How does the 
broker recover from that situation? 
   Does the Kubernetes detect the issue and kill the pod? Would it make sense 
to do the thread dump automatically at broker shutdown?


-- 
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]


Reply via email to