[
https://issues.apache.org/jira/browse/CASSANDRA-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999970#comment-13999970
]
Tyler Hobbs commented on CASSANDRA-7231:
----------------------------------------
Hmm, unfortunately using a flag makes it a little tough for the drivers to
automatically support this in a safe, backwards-compatible way. In 2.0, if you
use an unrecognized flag, it results in an ArrayIndexOutOfBoundsException
server-side, so a ServerError is the response. That's probably not a good
response to use to check whether this is supported.
Although I initially suggested using a flag, I think simply making this the v3
protocol behavior might be the better choice. It's easier for drivers to
support features based on protocol versions than C* versions. What downsides
are there to basing this on the protocol version?
> 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
>
>
> 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)
