cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Kramarenko (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1102) Call to loadbalance cause ava.lang.UnsupportedOperationException: data is currently moving to this node; unable to leave the ring
Date Mon, 17 May 2010 21:56:42 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maxim Kramarenko updated CASSANDRA-1102:
----------------------------------------

    Attachment: system.log.gz

System log, probably you can understand what happend there.

> Call to loadbalance cause ava.lang.UnsupportedOperationException: data is currently moving
to this node; unable to leave the ring
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1102
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1102
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.1
>         Environment: CentOS 5
> 2.6.18-164.15.1.el5 #1 SMP Wed Mar 17 11:30:06 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Maxim Kramarenko
>            Priority: Minor
>         Attachments: system.log.gz
>
>
> When I am trying to run loadbalance, I got the following error message:
> [root@cas2 bin]# sh nodetool -h localhost loadbalance
> Exception in thread "main" java.lang.UnsupportedOperationException: data is
> currently moving to this node; unable to leave the ring
> I am actually run loadbalance on another node, but it was 3-4 days ago, I
> have just 100GB data (3 nodes), so I expect that data relocate should be
> already done.
> streams show nothing interest too:
> ===
> [root@cas2 bin]# sh nodetool -h localhost streams
> Mode: Node is drained
> Nothing streaming to /172.19.0.30
> Not receiving any streams.
> [root@cas2 bin]#
> ===
> After cluster restart it works ok.

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


Mime
View raw message