[
https://issues.apache.org/jira/browse/CASSANDRA-18845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cameron Zemek updated CASSANDRA-18845:
--------------------------------------
Description:
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}
was:
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 >
0)
{
logger.debug("Gossip looks settled.");
numOkay++;
} {code}
> 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-3.11.patch
>
>
> 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]
