You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Arya Goudarzi (JIRA)" <ji...@apache.org> on 2010/07/14 22:50:50 UTC

[jira] Created: (CASSANDRA-1281) server restart while streaming causes other nodes to not update the ring status

server restart while streaming causes other nodes to not update the ring status
-------------------------------------------------------------------------------

                 Key: CASSANDRA-1281
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1281
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 0.7
         Environment: CentOS 5.2
Nightly Build July 14th
            Reporter: Arya Goudarzi


To move away from the stalled stream as explained in CASSANDRA-1221, I had to restart the node. After restart the node shows status Normal on the ring for itself, but other nodes still show "Leaving". For other nodes to be update their node status, I had to restart them. I had waited quiet few hours for it to get updated:

[agoudarzi@cas-test1 ~]$ nodetool --host=10.50.26.132 ring
Address         Status State   Load            Token                                       
                                       160348796167900510561059505917619274541    
10.50.26.134    Up     Normal  116.98 MB       32717880524093094169411234083126184860      
10.50.26.132    Up     Normal  58.59 MB        75101027859180840627831025901565139619      
10.50.26.133    Up     Normal  116.87 MB       160348796167900510561059505917619274541     
[agoudarzi@cas-test1 ~]$ nodetool --host=10.50.26.134 ring
Address         Status State   Load            Token                                       
                                       160348796167900510561059505917619274541    
10.50.26.134    Up     Normal  116.98 MB       32717880524093094169411234083126184860      
10.50.26.132    Up     Leaving 58.59 MB        75101027859180840627831025901565139619   <== Notice "Leaving". 132 was restart and back to Normal
10.50.26.133    Up     Normal  116.87 MB       160348796167900510561059505917619274541     

This may or may not have to do with issue in CASSANDRA-1221. Pardon if it seams the duplicate of the other one.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CASSANDRA-1281) server restart while streaming causes other nodes to not update the ring status

Posted by "Arya Goudarzi (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888596#action_12888596 ] 

Arya Goudarzi commented on CASSANDRA-1281:
------------------------------------------

What if the user decided to not re-issue the command? Maybe made a mistake initially and terminated the process?

> server restart while streaming causes other nodes to not update the ring status
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1281
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1281
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7
>         Environment: CentOS 5.2
> Nightly Build July 14th
>            Reporter: Arya Goudarzi
>
> To move away from the stalled stream as explained in CASSANDRA-1221, I had to restart the node. After restart the node shows status Normal on the ring for itself, but other nodes still show "Leaving". For other nodes to be update their node status, I had to restart them. I had waited quiet few hours for it to get updated:
> [agoudarzi@cas-test1 ~]$ nodetool --host=10.50.26.132 ring
> Address         Status State   Load            Token                                       
>                                        160348796167900510561059505917619274541    
> 10.50.26.134    Up     Normal  116.98 MB       32717880524093094169411234083126184860      
> 10.50.26.132    Up     Normal  58.59 MB        75101027859180840627831025901565139619      
> 10.50.26.133    Up     Normal  116.87 MB       160348796167900510561059505917619274541     
> [agoudarzi@cas-test1 ~]$ nodetool --host=10.50.26.134 ring
> Address         Status State   Load            Token                                       
>                                        160348796167900510561059505917619274541    
> 10.50.26.134    Up     Normal  116.98 MB       32717880524093094169411234083126184860      
> 10.50.26.132    Up     Leaving 58.59 MB        75101027859180840627831025901565139619   <== Notice "Leaving". 132 was restart and back to Normal
> 10.50.26.133    Up     Normal  116.87 MB       160348796167900510561059505917619274541     
> This may or may not have to do with issue in CASSANDRA-1221. Pardon if it seams the duplicate of the other one.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CASSANDRA-1281) server restart while streaming causes other nodes to not update the ring status

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-1281.
---------------------------------------

    Resolution: Not A Problem

this is expected.  what you should do is redo the command you were doing on the node that restarted.

> server restart while streaming causes other nodes to not update the ring status
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1281
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1281
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7
>         Environment: CentOS 5.2
> Nightly Build July 14th
>            Reporter: Arya Goudarzi
>
> To move away from the stalled stream as explained in CASSANDRA-1221, I had to restart the node. After restart the node shows status Normal on the ring for itself, but other nodes still show "Leaving". For other nodes to be update their node status, I had to restart them. I had waited quiet few hours for it to get updated:
> [agoudarzi@cas-test1 ~]$ nodetool --host=10.50.26.132 ring
> Address         Status State   Load            Token                                       
>                                        160348796167900510561059505917619274541    
> 10.50.26.134    Up     Normal  116.98 MB       32717880524093094169411234083126184860      
> 10.50.26.132    Up     Normal  58.59 MB        75101027859180840627831025901565139619      
> 10.50.26.133    Up     Normal  116.87 MB       160348796167900510561059505917619274541     
> [agoudarzi@cas-test1 ~]$ nodetool --host=10.50.26.134 ring
> Address         Status State   Load            Token                                       
>                                        160348796167900510561059505917619274541    
> 10.50.26.134    Up     Normal  116.98 MB       32717880524093094169411234083126184860      
> 10.50.26.132    Up     Leaving 58.59 MB        75101027859180840627831025901565139619   <== Notice "Leaving". 132 was restart and back to Normal
> 10.50.26.133    Up     Normal  116.87 MB       160348796167900510561059505917619274541     
> This may or may not have to do with issue in CASSANDRA-1221. Pardon if it seams the duplicate of the other one.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.