pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] rdhabalia commented on issue #3630: Broker can not respond to client requests
Date Fri, 22 Feb 2019 00:26:21 GMT
rdhabalia commented on issue #3630: Broker can not respond to client requests
URL: https://github.com/apache/pulsar/issues/3630#issuecomment-466224039
 
 
   > even if this deadlock occurs. However, I think it is ideal that this deadlock does
not occur.
   
   @massakam, we need to figure out the root cause the issue so, it won't happen again. However,
everytime I see deadlock, thread-dump showed that thread gets blocked while fetching data
from zk and it happened multiple times at broker so, i don't believe that zk-client is failing
this many times to return callback. However, I don't see any exception at that time which
can give us evident to understand this issue. So, I feel there has to be an issue at pulsar
app level rather zk-client level and I am looking into it to figure out actual root cause.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services

Mime
View raw message