[
https://issues.apache.org/jira/browse/CASSANDRA-16581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344794#comment-17344794
]
David Capwell commented on CASSANDRA-16581:
-------------------------------------------
the python details are failing now that we no longer fall back to highest
supported protocol version when an unknown protocol version is seen...
{code}
Unexpected error found in node logs (see stdout for full details). Errors:
[WARN [epollEventLoopGroup-5-5] 2021-05-14 16:59:18,418 NoSpamLogger.java:95 -
Protocol exception with client networking:
org.apache.cassandra.transport.ProtocolException: Invalid or unsupported
protocol version (66); supported versions are (3/v3, 4/v4, 5/v5, 6/v6-beta),
WARN [epollEventLoopGroup-5-6] 2021-05-14 16:59:18,418 NoSpamLogger.java:95 -
Protocol exception with client networking:
org.apache.cassandra.transport.ProtocolException: Invalid or unsupported
protocol version (65); supported versions are (3/v3, 4/v4, 5/v5, 6/v6-beta),
WARN [epollEventLoopGroup-5-5] 2021-05-14 16:59:18,418 NoSpamLogger.java:95 -
Protocol exception with client networking:
org.apache.cassandra.transport.ProtocolException: Invalid or unsupported
protocol version (66); supported versions are (3/v3, 4/v4, 5/v5, 6/v6-beta)]
{code}
I can replicate this when the following is done
{code}
$ ./bin/cqlsh
Connected to Test Cluster at 127.0.0.1:9042
[cqlsh 6.0.0 | Cassandra 4.1-SNAPSHOT | CQL spec 3.4.5 | Native protocol v5]
Use HELP for help.
cqlsh>
{code}
{code}
WARN [nioEventLoopGroup-5-10] 2021-05-14 10:56:18,366 NoSpamLogger.java:95 -
Protocol exception with client networking:
org.apache.cassandra.transport.ProtocolException: Invalid or unsupported
protocol version (65); supported versions are (3/v3, 4/v4, 5/v5, 6/v6-beta)
{code}
but this doesn't happen when I specify a specific version
{code}
$ ./bin/cqlsh --protocol-version 1
Connection error: ('Unable to connect to any servers', {'127.0.0.1:9042':
DriverException('ProtocolError returned from server while using explicitly set
client protocol_version 1')})
$ ./bin/cqlsh --protocol-version 2
Connection error: ('Unable to connect to any servers', {'127.0.0.1:9042':
DriverException('ProtocolError returned from server while using explicitly set
client protocol_version 2')})
$ ./bin/cqlsh --protocol-version 3
Connected to Test Cluster at 127.0.0.1:9042
[cqlsh 6.0.0 | Cassandra 4.1-SNAPSHOT | CQL spec 3.4.5 | Native protocol v3]
Use HELP for help.
cqlsh>
$ ./bin/cqlsh --protocol-version 4
Connected to Test Cluster at 127.0.0.1:9042
[cqlsh 6.0.0 | Cassandra 4.1-SNAPSHOT | CQL spec 3.4.5 | Native protocol v4]
Use HELP for help.
cqlsh>
$ ./bin/cqlsh --protocol-version 5
Connected to Test Cluster at 127.0.0.1:9042
[cqlsh 6.0.0 | Cassandra 4.1-SNAPSHOT | CQL spec 3.4.5 | Native protocol v5]
Use HELP for help.
cqlsh>
$ ./bin/cqlsh --protocol-version 6
Connection error: ('Unable to connect to any servers', {'127.0.0.1:9042':
<Error from server: code=000a [Protocol error] message="Beta version of the
protocol used (6/v6-beta), but USE_BETA flag is unset">})
{code}
{code}
WARN [nioEventLoopGroup-5-13] 2021-05-14 10:57:27,019 NoSpamLogger.java:95 -
Protocol exception with client networking:
org.apache.cassandra.transport.ProtocolException: Invalid or unsupported
protocol version (1); supported versions are (3/v3, 4/v4, 5/v5, 6/v6-beta)
WARN [nioEventLoopGroup-5-14] 2021-05-14 10:57:30,967 NoSpamLogger.java:95 -
Protocol exception with client networking:
org.apache.cassandra.transport.ProtocolException: Invalid or unsupported
protocol version (2); supported versions are (3/v3, 4/v4, 5/v5, 6/v6-beta)
WARN [nioEventLoopGroup-5-21] 2021-05-14 10:57:42,520 NoSpamLogger.java:95 -
Protocol exception with client networking:
org.apache.cassandra.transport.ProtocolException: Beta version of the protocol
used (6/v6-beta), but USE_BETA flag is unset
{code}
> Failure to execute queries should emit a KPI other than read
> timeout/unavailable so it can be alerted/tracked
> -------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16581
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16581
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client, Observability/Metrics
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0-rc
>
>
> When we are unable to parse a message we do not have a way to detect this
> from a monitoring point of view so can get into situations where we believe
> the database is fine but the clients are on-fire. This case popped up in the
> 2.1 to 3.0 upgrade as paging state wasn’t mixed-mode safe.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
