You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.
We are using the client to connect to a 3.4.6 zookeeper server. On connect, we get these warnings in the zk server log:
- Connection request from old client /127.0.0.1:51335; will be dropped if server is in r-o mode
Looking at the source code in ZooKeeperServer.java, there's this:
boolean readOnly = false;
try {
readOnly = bia.readBool("readOnly");
cnxn.isOldClient = false;
} catch (IOException e) {
// this is ok -- just a packet from an old client which
// doesn't contain readOnly field
LOG.warn("Connection request from old client "
+ cnxn.getRemoteSocketAddress()
+ "; will be dropped if server is in r-o mode");
}
It appears this is ok, but the client should probably be updated to look like a current client.
The text was updated successfully, but these errors were encountered:
Is there other changes that need to be made to support the read only mode? Or is it just different possible error states to handle if the server is set to read-only?
Would like to understand what the r-o mode means before sending the flag.
We are using the client to connect to a 3.4.6 zookeeper server. On connect, we get these warnings in the zk server log:
- Connection request from old client /127.0.0.1:51335; will be dropped if server is in r-o mode
Looking at the source code in ZooKeeperServer.java, there's this:
It appears this is ok, but the client should probably be updated to look like a current client.
The text was updated successfully, but these errors were encountered: