Re: String inconsistency issue when running ZK with OpenJDK 10 on SKL machines

2019-10-28 Thread Andor Molnar
Here’s the JDK issue that Fangmin mentioned: https://bugs.openjdk.java.net/browse/JDK-8207746 It’s a JDK 10 & 11 bug which has already been fixed since JDK11 b27. Andor > On 2019. Oct 28., at 8:00, Enrico Olivelli wrote: > > Fangmin, > > Il lun 28 ott 2019, 02:23 Fangmin Lv ha scritto: >

Re: Zookeeper 3.5.6 - Exception causing close of session 0x0: null

2019-10-28 Thread Sebastian Schmitz
Hello again, just as a final update on this. We had a weird consumer which someone updated without informing me... Turning it off also turned off the errors from spamming the logs. However it seems like the 3.5.6 is less informative than the 3.4.14 we had before as 3.4.14 also had the

Re: ZooKeeper Connection Timeout

2019-10-28 Thread Jordan Zimmerman
There is no such thing in ZooKeeper itself. Apache Curator simulates this by generating an error if the connection doesn't succeed within a given period of time. -JZ > On Oct 28, 2019, at 6:03 PM, V P wrote: > > Hello, > > Could someone please point me to a place in the documentation on how

ZooKeeper Connection Timeout

2019-10-28 Thread V P
Hello, Could someone please point me to a place in the documentation on how to configure ConnectionTimeout for a ZooKeeper client connection? (Note: What I'm asking is different from SessionTimeout) For example, if my ZK server is not available/not valid, is there a way for ZK client to stop

Re: Issue Workaround

2019-10-28 Thread Enrico Olivelli
Matthew, can you share some logs ? That issue is quite generic, and it describes a case that usually works as expected (= system works fine) It is very common to bounce a server in a cluster of three, so there must be a cause for your problem. In a 3 nodes clusters usually you can continue

Issue Workaround

2019-10-28 Thread Matthew Knight
Hi, I am setting up a 3-node Zookeeper cluster and have encountered the issue described in https://issues.apache.org/jira/browse/ZOOKEEPER-2164 It seems like Zookeeper is unable to recover if the leader node shuts down unexpectedly. Is this truly a general problem with Zookeeper? Is there a way

Re: Kerberos login error: Message stream modified (41)

2019-10-28 Thread Enrico Olivelli
Andor Il lun 28 ott 2019, 17:44 Andor Molnar ha scritto: > Hi, > > I’m facing the following error message when trying to run ZooKeeper 3.5.5 > on Java 11 with Kerberos authentication: > > 2019-10-28 16:30:04,811 INFO > org.apache.zookeeper.server.ServerCnxnFactory: Using >

Re: Can I use czxid as unique sequence number?

2019-10-28 Thread Andor Molnar
Yes, I think you can do that. zxid is currently an AtomicLong in the leader which we increment on every write request. Andor > On 2019. Oct 18., at 17:59, Vincent Ngan wrote: > > I want to determine the order of creation of a number of nodes without > using ZooKeeper's sequence feature

Re: String inconsistency issue when running ZK with OpenJDK 10 on SKL machines

2019-10-28 Thread Patrick Hunt
On Mon, Oct 28, 2019 at 12:06 AM Enrico Olivelli wrote: > Fangmin, > > Il lun 28 ott 2019, 02:23 Fangmin Lv ha scritto: > > > Hey everyone, > > > > (Forgot to add subject in the previous email, resent with clear subject.) > > > > I'd like to share some weird inconsistency bugs we saw recently

Kerberos login error: Message stream modified (41)

2019-10-28 Thread Andor Molnar
Hi, I’m facing the following error message when trying to run ZooKeeper 3.5.5 on Java 11 with Kerberos authentication: 2019-10-28 16:30:04,811 INFO org.apache.zookeeper.server.ServerCnxnFactory: Using org.apache.zookeeper.server.NIOServerCnxnFactory as server connection factory 2019-10-28

Re: String inconsistency issue when running ZK with OpenJDK 10 on SKL machines

2019-10-28 Thread Enrico Olivelli
Fangmin, Il lun 28 ott 2019, 02:23 Fangmin Lv ha scritto: > Hey everyone, > > (Forgot to add subject in the previous email, resent with clear subject.) > > I'd like to share some weird inconsistency bugs we saw recently on prod, > the root cause and potential fixes of it. It took us around a