[ https://issues.apache.org/jira/browse/CASSANDRA-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801518#comment-13801518 ]
Vijay commented on CASSANDRA-6206: ---------------------------------- v2 doesn't apply clean (in future may be use git patch). I will also change SSLFactory.getServerSocket to use this configuration. ping [~xedin] for HSHA for THRIFT-1868, Should we leave this ticket open till THRIFT-1868 gets resolved and/or also till 2.1 (changes the yaml configuration)? > 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.2 > > Attachments: cassandra.patch, cassandra-v2.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#6144)