cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gabriele renzi (JIRA)" <>
Subject [jira] Created: (CASSANDRA-939) Decommisioning does not update status
Date Thu, 01 Apr 2010 08:19:27 GMT
Decommisioning does not update status

                 Key: CASSANDRA-939
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 0.6
            Reporter: gabriele renzi
            Priority: Minor

This happened using 0.6-beta3 on a test two nodes cluster. 

Steps that lead to problem:

- launch node A
- load data in A
- launch node B connected to A
- load data in both (replicationfactor is 1)
- use nodetool to decommission A

At this point something went wrong inside A, and the command seemingly failed:

rff@A$ ./bin/nodetool --host localhost decommission
Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
        at $Proxy0.decommission(Unknown Source)
Caused by: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception
        at sun.rmi.transport.StreamRemoteCall.executeCall(
        at sun.rmi.server.UnicastRef.invoke(
        at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
        at Source)
        ... 3 more
Caused by:
        at sun.rmi.transport.StreamRemoteCall.executeCall(
        ... 8 more

At this point, `nodetool streams` on  A reported Mode:decommissioned but still sending streams.

The same way, node B still reported Mode: normal and still receiving streams .
In both case the streaming values where reported as 0/size-of-data for all the files.

Having turned off node A, after ~24 hours, node B still reports the same thing.

The decommissioning seems to have actually worked, but the status never got updated.

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

View raw message