You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2021/01/15 07:23:00 UTC
[jira] [Comment Edited] (CASSANDRA-16376) Response headers to
OPTION messages always have Stream ID of zero
[ https://issues.apache.org/jira/browse/CASSANDRA-16376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265190#comment-17265190 ]
Michael Semb Wever edited comment on CASSANDRA-16376 at 1/15/21, 7:22 AM:
--------------------------------------------------------------------------
some small nit [comment|https://github.com/beobal/cassandra/commit/2764a5f33ebe61e272c39ed9de3f38428c37089b], otherwise +1
was (Author: michaelsembwever):
some small nit comment, otherwise +1
> Response headers to OPTION messages always have Stream ID of zero
> ------------------------------------------------------------------
>
> Key: CASSANDRA-16376
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16376
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Paulius Bankauskas
> Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: cass-dump.pcap
>
>
> It seems that streaming behavior has changed since version 4.0-beta2. When a new connection is made, all responses to the OPTIONS messages always return with stream id 0 even if requests are made with stream id 1. This causes connection failures on some clients.
> Attached wireshark dump with an example.
>
> Node version: 4.0-beta4
> Native protocol version: tested with v3 and v4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org