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] [Updated] (CASSANDRA-6788) Race condition silently kills thrift server
Date Sat, 01 Mar 2014 21:07:19 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-6788:
--------------------------------------

    Attachment: 6788-v2.txt

I see.  But that doesn't eliminate the window for a race, just reduces it.  (TPE.runWorker
still needs to call afterExecute and do its own bookkeeping.)  v2 adds an explicit catch for
REE.  This is better than dying, but it will accept connections and then drop them on the
floor if necessary which is obviously sub optimal.  Moral is not to push right up to the edge
of max connections. :)

> Race condition silently kills thrift server
> -------------------------------------------
>
>                 Key: CASSANDRA-6788
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6788
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Christian Rolf
>            Assignee: Christian Rolf
>         Attachments: 6788-v2.txt, race_patch.diff
>
>
> There's a race condition in CustomTThreadPoolServer that can cause the thrift server
to silently stop listening for connections. 
> It happens when the executor service throws a RejectedExecutionException, which is not
caught.
>  
> Silent in the sense that OpsCenter doesn't notice any problem since JMX is still running
fine.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message