[
https://issues.apache.org/jira/browse/CASSANDRA-18845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836370#comment-17836370
]
Cameron Zemek edited comment on CASSANDRA-18845 at 4/11/24 10:18 PM:
---------------------------------------------------------------------
I have reworked the [patch| [^CASSANDRA-18845-4_0_12.patch]] more so it a new
method instead of modifying the existing waitToSettle, so it has the least
change to any existing behavior. It directly called in
MigrationCoordinator::awaitSchemaRequests to handle if node bootstrapping
(since need nodes in UP state in order to get schema and stream sstables from).
And just before enabling native transport.
was (Author: cam1982):
I have reworked the patch more so it a new method instead of modifying the
existing waitToSettle. So it has the least change to any existing behavior. It
directly called in MigrationCoordinator::awaitSchemaRequests to handle if node
bootstrapping (since need nodes in UP state in order to get schema and stream
sstables from). And just before enabling native transport.
https://issues.apache.org/jira/secure/attachment/13068153/CASSANDRA-18845-4_0_12.patch
> Waiting for gossip to settle on live endpoints
> ----------------------------------------------
>
> Key: CASSANDRA-18845
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18845
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Cameron Zemek
> Priority: Normal
> Attachments: 18845-seperate.patch, CASSANDRA-18845-4_0_12.patch,
> delay.log, example.log, image-2023-09-14-11-16-23-020.png, stream.log,
> test1.log, test2.log, test3.log
>
>
> This is a follow up to CASSANDRA-18543
> Although that ticket added ability to set cassandra.gossip_settle_min_wait_ms
> this is tedious and error prone. On a node just observed a 79 second gap
> between waiting for gossip and the first echo response to indicate a node is
> UP.
> The problem being that do not want to start Native Transport until gossip
> settles otherwise queries can fail consistency such as LOCAL_QUORUM as it
> thinks the replicas are still in DOWN state.
> Instead of having to set gossip_settle_min_wait_ms I am proposing that
> (outside single node cluster) wait for UP message from another node before
> considering gossip as settled. Eg.
> {code:java}
> if (currentSize == epSize && currentLive == liveSize && liveSize
> > 1)
> {
> logger.debug("Gossip looks settled.");
> numOkay++;
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
