cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radim Kolar (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-6032) shuffle fails with NumberFormatException
Date Sun, 15 Sep 2013 10:51:51 GMT
Radim Kolar created CASSANDRA-6032:

             Summary: shuffle fails with NumberFormatException
                 Key: CASSANDRA-6032
             Project: Cassandra
          Issue Type: Bug
          Components: Tools
            Reporter: Radim Kolar

 INFO 12:42:56,906 Removing RELOCATION state for / -6470120033327209844
 INFO 12:46:41,656 Enabling scheduled transfers of token ranges
 INFO 12:46:41,656 Initiating transfer of -6730365637522478358 (scheduled at Sun
 Sep 15 12:41:14 CEST 2013)
 WARN 12:46:41,656 cannot move -6730365637522478358; source and destination match
 WARN 12:46:41,656 no valid token arguments specified; nothing to relocate
ERROR 12:46:41,656 Error removing -6730365637522478358: java.lang.NumberFormatException: For
input string: ""
ERROR 12:46:41,875 Exception in thread Thread[GossipStage:1,5,main]
java.lang.NumberFormatException: For input string: ""
        at java.lang.NumberFormatException.forInputString(NumberFormatException.
        at java.lang.Long.parseLong(
        at java.lang.Long.valueOf(
        at org.apache.cassandra.dht.Murmur3Partitioner$1.fromString(Murmur3Parti
        at org.apache.cassandra.service.StorageService.handleStateRelocating(Sto
        at org.apache.cassandra.service.StorageService.onChange(StorageService.j
        at org.apache.cassandra.gms.Gossiper.doNotifications(
        at org.apache.cassandra.gms.Gossiper.applyNewStates(
        at org.apache.cassandra.gms.Gossiper.applyStateLocally(
        at org.apache.cassandra.gms.GossipDigestAckVerbHandler.doVerb(GossipDige
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
        at java.util.concurrent.ThreadPoolExecutor$

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message