[
https://issues.apache.org/jira/browse/CASSANDRA-15385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964996#comment-16964996
]
Aleksey Yeschenko commented on CASSANDRA-15385:
-----------------------------------------------
3.0: [code|https://github.com/iamaleksey/cassandra/commits/15385-3.0],
[CI|https://circleci.com/workflow-run/e202c2ef-6bba-453b-ac05-c8125b643683]
3.11: [code|https://github.com/iamaleksey/cassandra/commits/15385-3.11],
[CI|https://circleci.com/workflow-run/a0ce5ec1-b3c7-417e-97c9-7387a30d0ab5]
4.0: [code|https://github.com/iamaleksey/cassandra/commits/15385-4.0] (only
updates NEWS.txt)
dtest changes:
[here|https://github.com/iamaleksey/cassandra-dtest/commits/15385]
We do have a dtest that covers the issue - it's just that at the moment it
white-lists these exceptions and ignores them in the logs. The commit to dtest
repo forces the test to fail without the suggested changes to C*, but the test
passes cleanly with them, without any disconnects, message drops, and errors in
the logs. Running the test is a little involved, however, since running upgrade
tests is currently broken on Circle. I did run them locally however.
> Ensure that tracing doesn't break connections in 3.x/4.0 mixed mode by default
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-15385
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15385
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/Tracing
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
