This message was deleted.

Oh, We may not have realized that this was a particularly serious bug, nor caught it in time. The classmate of the PR of merge did not type 2.11.1 when he was labeling. At the same time, we were also publishing the version at that time, so this PR was not included.

Thanks a lot for your response. Yes, I also think it's a serious bug, especially when network encounters issues.

yes, I tested, it’s really a serious bug.

The regression was introduced in 2.10.4 IIRC

ok

@Mathieu G. We will cherry-pick the fix to release branches, 2.9, 2.11 and 2.11 and sorry about missing your PR in the patch release. So that we can ship the fix to the next patch release. BTW, It’s better to join the dev mailing list, we have pushed 2 release candidate for 2.11.1 release https://lists.apache.org/thread/w77j3zdyx3k2t0vxwpkm22hrrldcyojc https://lists.apache.org/thread/q1yqwq6shjy8dzd0p4dj6r791znptcfp And the release process is started before your PR, so the committer added the release label to the next patch release. Usually, if there is a regression, vote (-1) under the mailing thread, so that the release manager can start a new candidate with the regression fix. The next patch release will be planned to June. The 3.0.0 release is in-progress which will have the fix. It will be available in May. And there is no major changes introduced to the client side in 3.0.0, so I think you can try to upgrade to 3.0.0 (Java Client). Appreciate your contribution 😀

Thanks for your reply. I was wondering if I needed to release a self hosted patched version to workarround this bug, but, I'll give a try to client 3.0.0. Is it compatible with a 2.11 server ?

I'll give a try to client 3.0.0. Is it compatible with a 2.11 server ?

Yes, all client versions are supposed to work with all server versions, with the obvious exception that newer protocol features will not be available. When a client connects to the server, part of the handshake is to agree on a protocol version to use.