[
https://issues.apache.org/jira/browse/ZOOKEEPER-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872705#comment-17872705
]
Kezhu Wang commented on ZOOKEEPER-4814:
---------------------------------------
master: 90f8d835e065ea12dddd8ed9ca20872a4412c78a
branch-3.9: 4d68e3e56fadbee46907213449a0fe6da302e161
> 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
> Labels: pull-request-available
> Fix For: 3.10.0, 3.9.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
