cassandra-commits mailing list archives

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


Brandon Williams updated CASSANDRA-5815:

    Attachment: 5185.txt

Mostly this problem is cosmetic, but the crux of it is that in a couple of places we assume
that since we're in a call regarding an endpoint, the gossiper will always know about the
endpoint while we're in the call.  This isn't the case with fat clients though, which the
gossiper could expire at any time.  Patch to check that the gossiper actually still knows
about the endpoint to avoid the NPE.

> 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
>             Fix For: 1.2.12
>         Attachments: 5185.txt
> 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