cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5815) NPE from migration manager
Date Mon, 07 Oct 2013 15:42:44 GMT


Brandon Williams commented on CASSANDRA-5815:

It looks the same to me.  The good news is the error is purely cosmetic at this point, there's
nothing left to do if the gossiper has removed the node (not to mention it's a fat client)

> NPE from migration manager
> --------------------------
>                 Key: CASSANDRA-5815
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.12
>            Reporter: Vishy Kasar
>            Assignee: Brandon Williams
>            Priority: Minor
> In one of our production clusters we see this error often. Looking through the source,
Gossiper.instance.getEndpointStateForEndpoint(endpoint) is returning null for some end point.
De we need any config change on our end to resolve this? In any case, cassandra should be
updated to protect against this NPE.
> ERROR [OptionalTasks:1] 2013-07-24 13:40:38,972 (line 132)
Exception in thread Thread[OptionalTasks:1,5,main] 
> java.lang.NullPointerException 
> at org.apache.cassandra.service.MigrationManager$ 
> at java.util.concurrent.Executors$ 
> at java.util.concurrent.FutureTask$Sync.innerRun( 
> at 
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(

> at java.util.concurrent.ScheduledThreadPoolExecutor$

> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(

> at java.util.concurrent.ThreadPoolExecutor$ 
> at
> It turned out that the reason for NPE was we bootstrapped a node with the same token
as another node. Cassandra should not throw an NPE here but log a meaningful error message.

This message was sent by Atlassian JIRA

View raw message