I don’t have stack traces handy, but was able to eliminate the problem in our environment by updating Jetty to 9.4.24 (ZOOKEEPER-3638 backport).
Craig From: "Chris T." <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, January 21, 2020 at 5:09 AM To: "[email protected]" <[email protected]> Subject: Re: Admin server deadlocks? Yes, attached. On Tue, Jan 21, 2020 at 6:19 AM Enrico Olivelli <[email protected]<mailto:[email protected]>> wrote: Do you have a dump of the stack traces if the JVM during the problem? Enrico Il lun 20 gen 2020, 21:06 Cee Tee <[email protected]<mailto:[email protected]>> ha scritto: > Hey that sounds familiar, we do curl to the stats api and they pretty > consistently start to hang after a while (minutes to hours). > I thought it was something in our environment but I'm happy to read I'm > not > the only one. :) > I used to run a snapshot 3.6 that didn't suffer from this. It appeared > after 'upgrading' to the official 356. > Regards > Chris > > On 20 January 2020 20:54:51 Craig.Condit > <[email protected]<mailto:[email protected]>> wrote: > > > 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. The stack dumps we have done seem to indicate some sort of lock > > being held, probably by Jetty. This makes sense, as when we see the hang > > start, it happens for all URLs (even the root / 404 not found page). > > > > > > Has anyone encountered this? I was not able to find a related JIRA. > > > >
