[
https://issues.apache.org/jira/browse/CASSANDRA-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248890#comment-13248890
]
Tyler Patterson commented on CASSANDRA-4115:
--------------------------------------------
After testing a little more I found the following:
On 1.0.9 I get the following schema when sleeping 30 seconds after the
decommission:
{'00000000-0000-1000-0000-000000000000': ['127.0.0.1'],
'UNREACHABLE': ['127.0.0.2']}
On 1.1, this is the schema 30 seconds after the decommission:
{'59adb24e-f3cd-3e02-97f0-5b395827453f': ['127.0.0.1'],
'UNREACHABLE': ['127.0.0.2']}
If I increase the sleep after decommissioning from 30 to 90 seconds, then 1.0.9
now returns only one schema, while 1.1 still fails with the UNREACHABLE schema.
None of these tests were done with the recent patch.
> 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
