cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-5414) Unspecified initial_token with ByteOrderedPartitioner results in java.lang.NumberFormatException: Non-hex characters
Date Tue, 02 Apr 2013 11:15:15 GMT
Pas created CASSANDRA-5414:
------------------------------

             Summary: Unspecified initial_token with ByteOrderedPartitioner results in java.lang.NumberFormatException:
Non-hex characters
                 Key: CASSANDRA-5414
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5414
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.2.3
         Environment: Oracle JDK, java 1.7.0_07, amd64 (x86_64), on a Debian Squeeze, no virtual
nodes, nothing fancy.
            Reporter: Pas
            Priority: Minor


Using one seed, after adding the third node the fresh node chooses an illegal token, so it
can't bootstrap itself. So I had to specify initial_token on each host manually. (Which, as
far as I know, is recommended anyway for non-random partitioners.)


java.lang.NumberFormatException: Non-hex characters in ^@^V73797374656d5f61757468
        at org.apache.cassandra.utils.Hex.hexToBytes(Hex.java:60)
        at org.apache.cassandra.dht.AbstractByteOrderedPartitioner$1.fromString(AbstractByteOrderedPartitioner.java:167)
        at org.apache.cassandra.dht.BootStrapper$BootstrapTokenCallback.response(BootStrapper.java:230)
        at org.apache.cassandra.net.ResponseVerbHandler.doVerb(ResponseVerbHandler.java:45)
        at org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:59)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:722)




--
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: http://www.atlassian.com/software/jira

Mime
View raw message