[
https://issues.apache.org/jira/browse/CASSANDRA-17054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433796#comment-17433796
]
David Capwell commented on CASSANDRA-17054:
-------------------------------------------
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17054-trunk-D0BB41D6-69AC-42C7-B884-2B22CE33E742]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17054-trunk-D0BB41D6-69AC-42C7-B884-2B22CE33E742]|[build|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1247/]|
> v4+ protocol did not clean up client warnings, which caused leaking the state
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-17054
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17054
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> If you perform a query in v5, this will cause the STARTUP message to be
> handled in the netty thread, but the way this is done is by calling an
> internal API to dispatcher which requires the caller to clean up; but we do
> not clean up; at this point the netty thread will have a ClientWarn state
> populated. If you now perform the same query again, but with the v3
> protocol, this will pick up the state and try to serialize it, causing a
> client error (in java as java rejects the output from the server) saying that
> v3 may not have client warnings.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
