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

Brandon Williams commented on CASSANDRA-7036:
---------------------------------------------

That's a problem with the schema not being done propagating yet, some sleep 
before the first make_updates call should solve it.  There's a greater problem 
though, and that's stopping the node after draining and waiting for the other 
node to notice.  After CASSANDRA-3936, the draining node is marked down almost 
instantly, so when the stop call is made the 'x.x.x.x is now DOWN' message has 
already been logged and ccm hangs looking for it, since it only appears once.

> counter_tests.py:TestCounters.upgrade_test dtest hangs in 1.2, 2.0, 2.1
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-7036
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7036
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tests
>            Reporter: Michael Shuler
>            Assignee: Aleksey Yeschenko
>             Fix For: 2.1 rc1
>
>




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to