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 2020/10/26 17:30:46 UTC

[GitHub] [pulsar] pkumar-singh edited a comment on pull request #8351: Upgrade GRPC to 1.31 to avoid deadlock

pkumar-singh edited a comment on pull request #8351:
URL: https://github.com/apache/pulsar/pull/8351#issuecomment-716705610


   Well, The context is. I was running bookkeeper table service and I encounter this deadlock. As  can be seen from the call stack. org.apache.bookkeeper.statelib.impl.journal.AbstractStateStoreWithJournal.lambda$executeIO$16(AbstractStateStoreWithJournal.java:472).  And I saw the grpc/grpc-java#3084 issue too while digging around.
   Natural question could be if deadlock is reported while running apache bookkeeper table service why upgrade pulsar. 
   Reason is: They all are running as same k8s deployment. 
   
   How do I confirm upgrade to 1.31 fixes the deadlock. Well, I upgraded to 1.31 in the deployment and deadlock never happened otherwise used to happen within 2 minutes.
   
   Besides everything, sooner or later gRPC have to be updated in Apache Pulsar as well. Apache Pulsar running with gRPC 1.18 does have a deadlock. @lhotari 


----------------------------------------------------------------
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:
users@infra.apache.org