zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Enrico Olivelli <eolive...@gmail.com>
Subject Re: Is 3.5.5 client compatible with 3.4.x servers
Date Thu, 18 Jul 2019 06:39:05 GMT
I was not aware of that change.
I should say that I have been running HBase client with 3.5.x zk client and
3.4 servers for years without issues


Enrico

Il gio 18 lug 2019, 06:05 Göktürk Gezer <gokturk@alluxio.com> ha scritto:

> Thank you for the reference Micheal.
>
> I discovered a workaround by forcing Curator to not use container parents.
>
> *CuratorFramework.Builder.dontUseContainerParents()* does the trick, at
> least for *LeaderElection* recipe.
>
> Thanks,
> Gokturk
>
> On Wed, Jul 17, 2019, 8:26 PM Michael Han <hanm@apache.org> wrote:
>
> > In theory, they should be compatible. See backward compatibility section
> > https://cwiki.apache.org/confluence/display/ZOOKEEPER/ReleaseManagement
> >
> > (where Major is 3, Minor is 5 and Minor - 1 is 4, in this case).
> >
> > In practice, this one looks incompatible. The Op code 15 in 3.5.5 client
> > was added in https://issues.apache.org/jira/browse/ZOOKEEPER-1297 which
> > was
> > only committed to 3.5, not 3.4...
> >
> > On Wed, Jul 17, 2019 at 11:33 AM Göktürk Gezer <gokturk@alluxio.com>
> > wrote:
> >
> > > Gentle Ping!
> > > I noticed I forgot to mention that we are using java api for zk client.
> > In
> > > case it makes a difference.
> > >
> > > Thanks,
> > > Gokturk
> > >
> > > > On Jul 12, 2019, at 4:33 PM, Göktürk Gezer <gokturk@alluxio.com>
> > wrote:
> > > >
> > > > Hi Everyone,
> > > > I recently bumped zookeeper client version to 3.5.5 in order to make
> > use
> > > of new constructor with ZKClientConfig. (Via curator 4.2.0)
> > > > This apparently broke communicating with older ZK server at version
> > > 3.4.9. Is this expected?
> > > >
> > > > Client traces:
> > > > ClientCnxn - Opening socket connection to server
> > ReplicationFt-masters-1/
> > > 172.31.20.201:2181. Will not attempt to authenticate using SASL
> (unknown
> > > error)
> > > > 2019-07-12 23:20:30,875 INFO  ClientCnxn - Socket connection
> > > established, initiating session, client: /172.31.20.201:50028, server:
> > > ReplicationFt-masters-1/172.31.20.201:2181
> > > > 2019-07-12 23:20:30,876 INFO  ClientCnxn - Session establishment
> > > complete on server ReplicationFt-masters-1/172.31.20.201:2181,
> sessionid
> > > = 0x16be87b7d400004, negotiated timeout = 40000
> > > > 2019-07-12 23:20:30,876 INFO  ConnectionStateManager - State change:
> > > RECONNECTED
> > > > 2019-07-12 23:20:30,877 INFO  ClientCnxn - Unable to read additional
> > > data from server sessionid 0x16be87b7d400004, likely server has closed
> > > socket, closing socket connection and attempting reconnect
> > > > 2019-07-12 23:20:30,978 INFO  ConnectionStateManager - State change:
> > > SUSPENDED
> > > > 2019-07-12 23:20:32,724 INFO  ClientCnxn - Opening socket connection
> to
> > > server ReplicationFt-masters-1/172.31.20.201:2181. Will not attempt to
> > > authenticate using SASL (unknown error)
> > > > 2019-07-12 23:20:32,724 INFO  ClientCnxn - Socket connection
> > > established, initiating session, client: /172.31.20.201:50030, server:
> > > ReplicationFt-masters-1/172.31.20.201:2181
> > > > 2019-07-12 23:20:32,725 INFO  ClientCnxn - Session establishment
> > > complete on server ReplicationFt-masters-1/172.31.20.201:2181,
> sessionid
> > > = 0x16be87b7d400004, negotiated timeout = 40000
> > > > 2019-07-12 23:20:32,725 INFO  ConnectionStateManager - State change:
> > > RECONNECTED
> > > > 2019-07-12 23:20:32,726 INFO  AbstractPrimarySelector - Primary
> > selector
> > > transitioning to SECONDARY
> > > > 2019-07-12 23:20:32,727 INFO  ClientCnxn - Unable to read additional
> > > data from server sessionid 0x16be87b7d400004, likely server has closed
> > > socket, closing socket connection and attempting reconnect
> > > > 2019-07-12 23:20:32,827 INFO  ConnectionStateManager - State change:
> > > SUSPENDED
> > > > 2019-07-12 23:20:34,412 INFO  ClientCnxn - Opening socket connection
> to
> > > server ReplicationFt-masters-1/172.31.20.201:2181. Will not attempt to
> > > authenticate using SASL (unknown error)
> > > > 2019-07-12 23:20:34,412 INFO  ClientCnxn - Socket connection
> > > established, initiating session, client: /172.31.20.201:50032, server:
> > > ReplicationFt-masters-1/172.31.20.201:2181
> > > > 2019-07-12 23:20:34,413 INFO  ClientCnxn - Session establishment
> > > complete on server ReplicationFt-masters-1/172.31.20.201:2181,
> sessionid
> > > = 0x16be87b7d400004, negotiated timeout = 40000
> > > > 2019-07-12 23:20:34,413 INFO  ConnectionStateManager - State change:
> > > RECONNECTED
> > > > 2019-07-12 23:20:34,414 INFO  ClientCnxn - Unable to read additional
> > > data from server sessionid 0x16be87b7d400004, likely server has closed
> > > socket, closing socket connection and attempting reconnect
> > > >
> > > > Server traces:
> > > > 2019-07-12 23:20:56,564 [myid:] - INFO  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@192] - Accepted socket
> > > connection from /172.31.20.201:50092
> > > > 2019-07-12 23:20:56,564 [myid:] - INFO  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:ZooKeeperServer@921] - Client attempting to renew
> > > session 0x16be87b7d400004 at /172.31.20.201:50092
> > > > 2019-07-12 23:20:56,565 [myid:] - INFO  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:ZooKeeperServer@673] - Established session
> > > 0x16be87b7d400004 with negotiated timeout 40000 for client /
> > > 172.31.20.201:50092
> > > > 2019-07-12 23:20:56,566 [myid:] - WARN  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:ZooKeeperServer@735] - Received packet at server
> of
> > > unknown type 15
> > > > 2019-07-12 23:20:56,566 [myid:] - INFO  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1008] - Closed socket connection
> for
> > > client /172.31.20.201:50092 which had sessionid 0x16be87b7d400004
> > > > 2019-07-12 23:20:56,566 [myid:] - ERROR
> [SyncThread:0:NIOServerCnxn@178
> > ]
> > > - Unexpected Exception:
> > > > java.nio.channels.CancelledKeyException
> > > >       at
> > > sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:73)
> > > >       at
> > > sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:77)
> > > >       at
> > >
> >
> org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:151)
> > > >       at
> > >
> >
> org.apache.zookeeper.server.NIOServerCnxn.sendResponse(NIOServerCnxn.java:1082)
> > > >       at
> > >
> >
> org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:391)
> > > >       at
> > >
> >
> org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:169)
> > > > 2019-07-12 23:20:57,752 [myid:] - INFO  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@192] - Accepted socket
> > > connection from /172.31.20.201:50094
> > > > 2019-07-12 23:20:57,753 [myid:] - INFO  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:ZooKeeperServer@921] - Client attempting to renew
> > > session 0x16be87b7d400004 at /172.31.20.201:50094
> > > > 2019-07-12 23:20:57,753 [myid:] - INFO  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:ZooKeeperServer@673] - Established session
> > > 0x16be87b7d400004 with negotiated timeout 40000 for client /
> > > 172.31.20.201:50094
> > > > 2019-07-12 23:20:57,754 [myid:] - WARN  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:ZooKeeperServer@735] - Received packet at server
> of
> > > unknown type 15
> > > > 2019-07-12 23:20:57,755 [myid:] - INFO  [NIOServerCxn.Factory:
> > > 0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1008] - Closed socket connection
> for
> > > client /172.31.20.201:50094 which had sessionid 0x16be87b7d400004
> > > >
> > > >
> > > > Thanks,
> > > > Gokturk
> > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message