You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2020/01/20 20:42:00 UTC

[jira] [Created] (ZOOKEEPER-3702) AdminServer stops responding (possible deadlock)

Craig Condit created ZOOKEEPER-3702:
---------------------------------------

             Summary: AdminServer stops responding (possible deadlock)
                 Key: ZOOKEEPER-3702
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3702
             Project: ZooKeeper
          Issue Type: Bug
          Components: server
    Affects Versions: 3.5.6
         Environment: CentOS 7.x, JDK 8 (various patch levels)
            Reporter: Craig Condit


We have been running Zookeeper 3.5.6 on several clusters for a while now, and have noticed (pretty consistently) that the new Admin Server seems to stop responding (hangs) after the ZK service has been up and running for a while. I'm not sure what causes this, but it seems to happen fairly reliably after some time (sometimes 10 minutes or more). This manifests as curl (or any other HTTP client) hanging while attempting to access any URL from the admin server port, even the top level which normally just returns a generic Jetty 404 error.

Possibly this was triggered by a Jetty version update?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)