You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2023/04/05 18:44:00 UTC

[jira] [Assigned] (CASSANDRA-18430) When decommissioning should set Severity to limit traffic

     [ https://issues.apache.org/jira/browse/CASSANDRA-18430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Capwell reassigned CASSANDRA-18430:
-----------------------------------------

    Assignee: David Capwell

> 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
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org