You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Pavel Yaskevich (JIRA)" <ji...@apache.org> on 2013/12/20 00:30:09 UTC

[jira] [Comment Edited] (CASSANDRA-6206) Thrift socket listen backlog

    [ https://issues.apache.org/jira/browse/CASSANDRA-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853457#comment-13853457 ] 

Pavel Yaskevich edited comment on CASSANDRA-6206 at 12/19/13 11:29 PM:
-----------------------------------------------------------------------

We are waiting for Thrift guys to resolve on their side first.


was (Author: xedin):
We are waiting for Thrift guys to resolve on their part first.

> 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.4
>
>         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.1.4#6159)