You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "John Knost (JIRA)" <ji...@apache.org> on 2018/07/20 18:39:00 UTC
[jira] [Updated] (CASSANDRA-14577) gc_grace_seconds should include
UJ (Up/Joining) status period
[ https://issues.apache.org/jira/browse/CASSANDRA-14577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Knost updated CASSANDRA-14577:
-----------------------------------
Environment: Contrail 3.0.3.3-22/Cassandra 2.1.13 (was: Issue observed in environment running Contrail 3.0.3.3-22/Cassandra 2.1.13)
> gc_grace_seconds should include UJ (Up/Joining) status period
> --------------------------------------------------------------
>
> Key: CASSANDRA-14577
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14577
> Project: Cassandra
> Issue Type: Improvement
> Components: Coordination
> Environment: Contrail 3.0.3.3-22/Cassandra 2.1.13
> Reporter: John Knost
> Priority: Major
>
> Partial network connectivity (e.g. and MTU mismatch that blackholes jumbo frames) can cause a node to get stuck in a permanent UJ status (as reflected in nodetool). It's possible the node can stay in this way for an extended period of time. Once the isolated node rejoins due to a network repair, it can cause extensive data loss to the healthy nodes.
>
> If the node were completely isolated gc_grace_seconds would prevent the node from joining after the specified period. Other corner cases besides "DN" should be covered if applicable.
>
> Reference:
> JTAC 2018-0303-0029
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org