[
https://issues.apache.org/jira/browse/CASSANDRA-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-4115:
----------------------------------------
Attachment: 4115.txt
The only way I can see this happening on 1.0 is if ring delay is set to
something lower than the gossip interval *2, otherwise it might not actually
send the 'left' message. That would result in the node being stuck in a
'leaving' and down state keeping it in the unreachable map.
For 1.1 and trunk, this is caused by CASSANDRA-3936, forcing a conviction when
the decom node shuts the gossiper down, after the others have already removed
it. Instead, markAlive and markDead should have a dead state check and thus
ignore it, since it's never valid to do either with a dead state.
> UNREACHABLE schema after decommissioning a non-seed node
> --------------------------------------------------------
>
> Key: CASSANDRA-4115
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4115
> Project: Cassandra
> Issue Type: Bug
> Environment: ccm using the following unavailable_schema_test.py dtest.
> Reporter: Tyler Patterson
> Assignee: Brandon Williams
> Priority: Minor
> Attachments: 4115.txt
>
>
> decommission a non-seed node, sleep 30 seconds, then use thrift to check the
> schema. UNREACHABLE is listed:
> {'75dc4c07-3c1a-3013-ad7d-11fb34208465': ['127.0.0.1'],
> 'UNREACHABLE': ['127.0.0.2']}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
