[Curator] about isOwnedByCurrentThread() in InterProcessSemaphoreMutex

Hi Zookeeper/ Curator users and developers, I have a question regarding this method: isOwnedByCurrentThread() in InterProcessSemaphoreMutex in Curator https://curator.apache.org/apidocs/org/apache/curator/framework/recipes/locks/InterProcessSemaphoreMutex.html#isAcquiredInThisProcess-- If

Hazelcast claims

FYI https://hazelcast.com/long-live-distributed-locks/ I've only taken a quick look but this post is making a lot of claims. In particular, "To the best of our knowledge, FencedLock is the first open source distributed lock implementation

Re: Unexpected delay between pings sent from the client to server

Another couple of things I found: *A couple of Zookeeper client threads are stuck at these stacktraces for ~30 seconds* "pool-2-thread-1-EventThread" #1218 daemon prio=5 os_prio=0 tid=0x7ff3f5e23800 nid=0x5cd8 waiting on condition [0x7ff3ef803000] java.lang.Thread.State: WAITING

Zookeeper monitoring

Hello all, I order to set to correct values for several monitoring parameters, I would like to know the best value to monitor for following parameter: (from what value would it be necessary to worry about the following parameters) zk_outstanding_requests zk_open_file_descriptor_count

Unexpected delay between pings sent from the client to server

I'm trying to debug a problem where our client application suddenly loses its Zookeeper session. I concluded that by looking at the Zookeeper server logs. I increased the logging details for the client and found the following log messages > DEBUG: [07:33:33] [demo | HA | Manager] Got ping