[
https://issues.apache.org/jira/browse/CASSANDRA-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001480#comment-14001480
]
Sylvain Lebresne commented on CASSANDRA-7231:
---------------------------------------------
You misunderstood me, I didn't said that drivers *should* base support of this
on the Cassandra version. This is a protocol v3 feature and it's only
documented in the v3 spec. All I said is that because this happen to be
backward compatible I didn't bothered to reject request from the v1/v2 protocol
if they end up using this. If we're freaked out that some v1/v2 driver will use
this "by mistake" and get extra confused, I'm absolutely fine adding a protocol
version check and throw a ProtocolException.
But having it a flag means drivers that want to implement the v3 protocol don't
have to support this right away, they can do it in their own time, which is a
nice property to have.
> 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)
