merlimat commented on PR #22841:
URL: https://github.com/apache/pulsar/pull/22841#issuecomment-2148367070

   I don't think this is caused by having a single-thread processing the 
metadata-store callbacks (which should be typically solved by avoiding mixing 
sync/async calls). 
   
   In this case it looks just a deadlock in the `BookieRackAffinityMapping` 
code. The blocking of the metadata-callback thread is purely a side effect of 
the `ManagedLedgerFactoryImpl` map lock being held by the other thread. 
   
   It would be useful to see which thread is holding that lock: 
   
   ```
           - parking to wait for  <0x00001000f838ac60> (a 
java.util.concurrent.CompletableFuture$Signaller)
   ```
   
   Can you search for it in the full stack trace?


-- 
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-unsubscr...@pulsar.apache.org

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

Reply via email to