cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt Greaves (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13851) Allow existing nodes to use all peers in shadow round
Date Mon, 18 Sep 2017 05:09:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169592#comment-16169592
] 

Kurt Greaves commented on CASSANDRA-13851:
------------------------------------------

Certainly agree we should make operators aware of that. Let's most definitely not do that
by surprise "you can't start C*". Those are the worst types of surprise. Just needs a warning
on startup that no live seeds are configured IMO.
I'll probably have a crack at this after NGCC, not going to assign myself to it yet though
in case someone else wants to have at it.

> Allow existing nodes to use all peers in shadow round
> -----------------------------------------------------
>
>                 Key: CASSANDRA-13851
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13851
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Kurt Greaves
>
> In CASSANDRA-10134 we made collision checks necessary on every startup. A side-effect
was introduced that then requires a nodes seeds to be contacted on every startup. Prior to
this change an existing node could start up regardless whether it could contact a seed node
or not (because checkForEndpointCollision() was only called for bootstrapping nodes). 
> Now if a nodes seeds are removed/deleted/fail it will no longer be able to start up until
live seeds are configured (or itself is made a seed), even though it already knows about the
rest of the ring. This is inconvenient for operators and has the potential to cause some nasty
surprises and increase downtime.
> One solution would be to use all a nodes existing peers as seeds in the shadow round.
Not a Gossip guru though so not sure of implications.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message