cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nk11 (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CASSANDRA-114) exception when a node is joining
Date Thu, 30 Apr 2009 16:06:30 GMT

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

nk11 resolved CASSANDRA-114.
----------------------------

    Resolution: Fixed

> exception when a node is joining
> --------------------------------
>
>                 Key: CASSANDRA-114
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-114
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: nk11
>            Assignee: Jonathan Ellis
>             Fix For: 0.4
>
>         Attachments: 114-v2.patch, 115.patch
>
>
> When a new node is joining, StorageService is notified and the log shows this:
> java.lang.NumberFormatException: For input string: "T"
>         at java.lang.NumberFormatException.forInputString(Unknown Source)
>         at java.lang.Integer.parseInt(Unknown Source)
>         at java.math.BigInteger.<init>(Unknown Source)
>         at java.math.BigInteger.<init>(Unknown Source)
>         at org.apache.cassandra.dht.RandomPartitioner$3.fromString(RandomPartitioner.java:97)
>         at org.apache.cassandra.service.StorageService.onChange(StorageService.java:646)
>         at org.apache.cassandra.gms.Gossiper.doNotifications(Gossiper.java:770)
>         at org.apache.cassandra.gms.Gossiper.handleNewJoin(Gossiper.java:644)
> In my case, the EndPointState had a nodeIdState who's state_ was "Token(165385238122940489124770581854348071118)"
and produced the exception.

-- 
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