[
https://issues.apache.org/jira/browse/CASSANDRA-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934251#comment-13934251
]
Pavel Yaskevich commented on CASSANDRA-6206:
--------------------------------------------
The problem is that we have no control over socket.bind(...) call in depths of
TNonblockingServerSocket, we need Thrift guys to give us the way to set backlog
the same way as for blocking ones, so I don't think that's going in any time
soon. On the othre hand, we can easily cherry-pick blacklog to 2.0 but it would
only work with TThreadPoolServer so I'm not sure if it's that useful...
> 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.7
>
> 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)
