[
https://issues.apache.org/jira/browse/CASSANDRA-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006603#comment-14006603
]
Tyler Hobbs commented on CASSANDRA-7231:
----------------------------------------
It looks like there's one other bug in the patch
* In decode(), bodyLength is decremented if EXTENDED_STREAM_ID is set. That
should remain unchanged because the streamId byte isn't included in the body
length. However, I believe frameLength _should_ be incremented there.
bq. But the approach in this v1 I don't like - it's a bit too complex and
hackish. If you don't feel like cooking up another patch for this, I'll do it,
with either approach (1 - fixed 2-bytes or 2 - 8/9 bytes header depending on
the flag, described above), assuming that you don't disagree on principle
+1 (I still prefer the fixed 2 bytes)
> Support more concurrent requests per native transport connection
> ----------------------------------------------------------------
>
> Key: CASSANDRA-7231
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7231
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 2.1.0
>
> Attachments: 7231.txt, v1-doc-fixes.txt
>
>
> Right now we only support 127 concurrent requests against a given native
> transport connection. This causes us to waste file handles opening multiple
> connections, increases driver complexity and dilutes writes across multiple
> connections so that batching cannot easily be performed.
> I propose raising this limit substantially, to somewhere in the region of
> 16-64K, and that this is a good time to do it since we're already bumping the
> protocol version.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
