cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Anastasyev (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8138) replace_address cannot find node to be replaced node after seed node restart
Date Mon, 20 Oct 2014 20:01:34 GMT


Oleg Anastasyev commented on CASSANDRA-8138:

ah, sorry, a misleaded description. 

whole cluster was restarted, so failed node never participated in gossip since cluster startup.
not restart of one of seeds. fixed description

> replace_address cannot find node to be replaced node after seed node restart
> ----------------------------------------------------------------------------
>                 Key: CASSANDRA-8138
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Oleg Anastasyev
>         Attachments: ReplaceAfterSeedRestart.txt
> If a node failed and a cluster (or one of seeds) was restarted (which is common case
on massive outages), replace_address fails with
> {code}
> Caused by: java.lang.RuntimeException: Cannot replace_address / because it
doesn't exist in gossip
> jvm 1    | 	at org.apache.cassandra.service.StorageService.prepareReplacementInfo(
> jvm 1    | 	at org.apache.cassandra.service.StorageService.joinTokenRing(
> jvm 1    | 	at org.apache.cassandra.service.StorageService.initServer(
> jvm 1    | 	at org.apache.cassandra.service.StorageService.initServer(
> {code}
> Although neccessary information is saved in system tables on seed nodes, it is not loaded
to gossip on seed node, so a replacement node cannot get this info.
> Attached patch loads all information from system tables to gossip with generation 0 and
fixes some bugs around this info on shadow gossip round.

This message was sent by Atlassian JIRA

View raw message