curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordan Zimmerman <jor...@jordanzimmerman.com>
Subject Re: Heavy CPU consumption on CuratorZookeeperClient.internalBlockUntilConnectedOrTimedOut
Date Wed, 16 Oct 2013 18:00:33 GMT
CountDownLatch countDown is a blocking operation. So, it's not possible that it's consuming
CPU. I'm sure this is an issue with something else in the VM.

-JZ

On Oct 15, 2013, at 5:56 PM, "Bae, Jae Hyeon" <metacret@gmail.com> wrote:

> Hi
> 
> I got reported from a curator user about heavy CPU consumption on CuratorZookeeperClient.internalBlockUntilConnectedOrTimedOut()
specifically on latch.countDown().
> 
> I don't have any stack trace and CPU summary but may I know if this is known issue or
fixed in 2.2.0-incubating version?
> 
> Thank you
> Best, Jae


Mime
View raw message