[
https://issues.apache.org/jira/browse/CASSANDRA-13851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16294501#comment-16294501
]
Kurt Greaves edited comment on CASSANDRA-13851 at 12/19/17 4:25 AM:
--------------------------------------------------------------------
|[dtest|https://github.com/apache/cassandra-dtest/compare/master...kgreav:13851]|[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...kgreav:3.11-13851][utests|https://circleci.com/gh/kgreav/cassandra/51]|
Updated the patch so that a node that's not a seed won't be able to start if it
can't contact any peers. TBH I don't think this is the best solution as it's
still in part a regression on the old behaviour and requires you startup seeds
first in a full cluster bounce, but if anyone still sees that as a major issue
it can be done in a separate ticket as it's likely a bit of refactoring.
dtest has also been updated.
was (Author: kurtg):
|[dtest|https://github.com/apache/cassandra-dtest/compare/master...kgreav:13851]|[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...kgreav:3.11-13851]|
Updated the patch so that a node that's not a seed won't be able to start if it
can't contact any peers. TBH I don't think this is the best solution as it's
still in part a regression on the old behaviour and requires you startup seeds
first in a full cluster bounce, but if anyone still sees that as a major issue
it can be done in a separate ticket as it's likely a bit of refactoring.
dtest has also been updated.
> 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
> Components: Lifecycle
> Reporter: Kurt Greaves
> Assignee: Kurt Greaves
> Fix For: 3.11.x, 4.x
>
>
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
