cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1663) Allow configuration of thrift socket backlog
Date Mon, 25 Oct 2010 21:24:19 GMT

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

Jonathan Ellis commented on CASSANDRA-1663:
-------------------------------------------

We can add a configuration setting, but isn't the right solution to pool connections client-side?

> Allow configuration of thrift socket backlog
> --------------------------------------------
>
>                 Key: CASSANDRA-1663
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1663
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Dave Revell
>            Priority: Minor
>
> It would be nice to allow configuration of the Thrift server socket's listen backlog
size. The current limit is sometimes reached on my servers. I believe Thrift uses the ServerSocket
default, which is 50 pending sockets.
> This might be able to merge with CASSANDRA-1405, which also involves thrift socket changes.
> When connection volume is high, Cassandra fails to accept some connections because the
socket listen backlog is full. This happens to about 0.1% of connections in my case. System
load and IO are very low, so this does not seem to be a capacity problem.
> Helpful tip: on my Centos 5 box with kernel 2.6.18, the kernel exposes the number of
socket listen queue overflows in netstat. You can do e.g.:
> {noformat}
> # netstat -s | grep 'listen queue'
>     123 times the listen queue of a socket overflowed
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message