[
https://issues.apache.org/jira/browse/CASSANDRA-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917924#comment-13917924
]
Sylvain Lebresne commented on CASSANDRA-6206:
---------------------------------------------
What part of this exactly requires THRIFT-1868? Is the "Committed to trunk"
means that this is fixed in 2.1 but cannot be fixed in 2.0 without THRIFT-1868?
Cause that thrift ticket has had a patch waiting for review since last
September. I've pinged them on the issue, but if there is no movement soon and
that we're good in 2.1, maybe we should just say that it's 'fix for' 2.1 and
move on.
> Thrift socket listen backlog
> ----------------------------
>
> Key: CASSANDRA-6206
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6206
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Debian Linux, Java 7
> Reporter: Nenad Merdanovic
> Fix For: 2.0.6
>
> Attachments: cassandra-v2.patch, cassandra.patch
>
>
> Although Thrift is a depreciated method of accessing Cassandra, default
> backlog is way too low on that socket. It shouldn't be a problem to implement
> it and I am including a POC patch for this (sorry, really low on time with
> limited Java knowledge so just to give an idea).
> This is an old report which was never addressed and the bug remains till this
> day, except in my case I have a much larger scale application with 3rd party
> software which I cannot modify to include connection pooling:
> https://issues.apache.org/jira/browse/CASSANDRA-1663
> There is also a pending change in the Thrift itself which Cassandra should be
> able to use for parts using TServerSocket (SSL):
> https://issues.apache.org/jira/browse/THRIFT-1868
--
This message was sent by Atlassian JIRA
(v6.2#6252)
