[ https://issues.apache.org/jira/browse/ZOOKEEPER-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824461#comment-17824461 ]
Damien Diederen commented on ZOOKEEPER-4814: -------------------------------------------- Also related: [ClickHouse ticket, "Incompatibility with Zookeeper 3.9"|https://github.com/ClickHouse/ClickHouse/issues/53749] whose custom (?) client was updated by [patch "Add support for read-only mode in ZooKeeper"|https://github.com/ClickHouse/ClickHouse/pull/57479/files]. > Protocol desynchronization after Connect for (some) old clients > --------------------------------------------------------------- > > Key: ZOOKEEPER-4814 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4814 > Project: ZooKeeper > Issue Type: Bug > Components: server > Affects Versions: 3.9.0 > Reporter: Damien Diederen > Assignee: Damien Diederen > Priority: Major > > Some old clients experience a protocol synchronization after receiving a > {{ConnectResponse}} from the server. > This started happening with ZOOKEEPER-4492, "Merge readOnly field into > ConnectRequest and Response," which writes overlong responses to clients > which do not know about the {{readOnly}} flag. > (One example of such a client is ZooKeeper's own C client library prior to > version 3.5!) -- This message was sent by Atlassian Jira (v8.20.10#820010)