[
https://issues.apache.org/jira/browse/CASSANDRA-18430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18430:
-----------------------------------------
Status: Review In Progress (was: Patch Available)
> When decommissioning should set Severity to limit traffic
> ---------------------------------------------------------
>
> Key: CASSANDRA-18430
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18430
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Coordination
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> When we are decommissioning we first set LEAVING, then LEFT, then disable
> networking; timeouts start to follow at this last stage. LEFT nodes should
> not be seen as part of the ring, but that may not be seen before the network
> is disabled. To better mitigate timeouts we should set severity as part of
> decom during the LEAVING phase; by setting severity reads should deprioritize
> traffic to this node.
> Remote DC writes do not leverage proximity or severity and instead use random
> for its select, writes may still timeout even though we know the node is
> leaving, and severity is set… to work in this model we should update remote
> DC writes to deprioritize nodes with severity set
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
