[jira] [Commented] (CASSANDRA-4115) UNREACHABLE schema after decommissioning a non-seed node

2012-05-22 Thread Vijay (JIRA) 

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

Vijay commented on CASSANDRA-4115:
--

+1

> 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
>  Components: Core
>Affects Versions: 1.1.1
> Environment: ccm using the following unavailable_schema_test.py dtest.
>Reporter: Tyler Patterson
>Assignee: Brandon Williams
>Priority: Blocker
> Fix For: 1.1.1
>
> Attachments: 4115-v2.txt, 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

[jira] [Commented] (CASSANDRA-4115) UNREACHABLE schema after decommissioning a non-seed node

2012-05-21 Thread Vijay (JIRA) 

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

Vijay commented on CASSANDRA-4115:
--

I think we will have a problem in handleMajorStateChange

{code}
if (!isDeadState(epState))
markAlive(ep, epState);
else
{
logger.debug("Not marking " + ep + " alive due to dead state");
markDead(ep, epState);
}
{code}

but in markDead we have the following so it will never be marked dead.

{code}

if (isDeadState(localState))
return;
{code}

> 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
>  Components: Core
>Affects Versions: 1.1.1
> Environment: ccm using the following unavailable_schema_test.py dtest.
>Reporter: Tyler Patterson
>Assignee: Brandon Williams
>Priority: Blocker
> Fix For: 1.1.1
>
> 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

[jira] [Commented] (CASSANDRA-4115) UNREACHABLE schema after decommissioning a non-seed node

2012-04-12 Thread Brandon Williams (Commented) (JIRA) 

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

Brandon Williams commented on CASSANDRA-4115:
-

What does strike me as odd though is that your 1.0 test has no schema at all, 
hence the --1000-- uuid.

> 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

[jira] [Commented] (CASSANDRA-4115) UNREACHABLE schema after decommissioning a non-seed node

2012-04-12 Thread Brandon Williams (Commented) (JIRA) 

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

Brandon Williams commented on CASSANDRA-4115:
-

This must be something with the environment, on 1.0 I see the node removed as 
soon as the decom node begins to announce it has left (before it has completed 
announcing, and thus before nodetool would even return) and it never reappears.

> 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

[jira] [Commented] (CASSANDRA-4115) UNREACHABLE schema after decommissioning a non-seed node

2012-04-06 Thread Tyler Patterson (Commented) (JIRA) 

[ 
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:
{'--1000--': ['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

[jira] [Commented] (CASSANDRA-4115) UNREACHABLE schema after decommissioning a non-seed node

2012-04-06 Thread Jonathan Ellis (Commented) (JIRA) 

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

Jonathan Ellis commented on CASSANDRA-4115:
---

bq. 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

Pretty sure Tyler didn't mess with ring delay.

> 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

[jira] [Commented] (CASSANDRA-4115) UNREACHABLE schema after decommissioning a non-seed node

2012-04-04 Thread Tyler Patterson (Commented) (JIRA) 

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

Tyler Patterson commented on CASSANDRA-4115:


I tested and got it on branch 1.0.9-tentative and release 1.0.8.

I added unavailable_schema_test.py to the master branch of dtest.

> 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
>
> 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

[jira] [Commented] (CASSANDRA-4115) UNREACHABLE schema after decommissioning a non-seed node

2012-04-04 Thread Jonathan Ellis (Commented) (JIRA) 

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

Jonathan Ellis commented on CASSANDRA-4115:
---

Also, did you mean to attach unavailable_schema_test.py somewhere?

> 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
>
> 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