[ 
https://issues.apache.org/jira/browse/CASSANDRA-18430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711984#comment-17711984
 ] 

David Capwell commented on CASSANDRA-18430:
-------------------------------------------

[~brandon.williams] thanks for running, I only ran with PAID, so guess there is 
some issue with FREE?

{code}
[junit-timeout] WARN  16:13:34 Dropping message (from:/127.0.0.8:7012, 
type:MUTATION verb:MUTATI

********************************************************************************************************
This step produced more than the 100 MB limit of output, additional output will 
not be recorded.
If you need this amount of output, we suggest writing it to a file and using 
store_artifacts to save it.
********************************************************************************************************

Exited with code exit status 1
{code}

Heh, not a lot of details to go off of...

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to