cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-2072) Race condition during decommission
Date Mon, 31 Jan 2011 19:46:29 GMT


Brandon Williams updated CASSANDRA-2072:

    Attachment: 0003-Remove-endpoint-state-when-expiring-justRemovedEndpo.patch

> Race condition during decommission
> ----------------------------------
>                 Key: CASSANDRA-2072
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>         Attachments: 0001-announce-having-left-the-ring-for-RING_DELAY-on-deco.patch,
0002-Improve-TRACE-logging-for-Gossiper.patch, 0003-Remove-endpoint-state-when-expiring-justRemovedEndpo.patch
> Occasionally when decommissioning a node, there is a race condition that occurs where
another node will never remove the token and thus propagate it again with a state of down.
 With CASSANDRA-1900 we can solve this, but it shouldn't occur in the first place.
> Given nodes A, B, and C, if you decommission B it will stream to A and C.  When complete,
B will decommission and receive this stacktrace:
> ERROR 00:02:40,282 Fatal exception in thread Thread[Thread-5,5,main]
> java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut down
>         at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(
>         at java.util.concurrent.ThreadPoolExecutor.reject(
>         at java.util.concurrent.ThreadPoolExecutor.execute(
>         at
>         at
> At this point A will show it is removing B's token, but C will not and instead its failure
detector will report that B is dead, and nodetool ring on C shows B in a leaving/down state.
 In another gossip round, C will propagate this state back to A.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message