[
https://issues.apache.org/jira/browse/CASSANDRA-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuriy Semchyshyn updated CASSANDRA-18373:
-----------------------------------------
Description:
SS tables imports that will end up being ignored due to the node draining
should fail instead of succeeding.
Each active SS tables import should periodically check for the node status and
see whether or not it is `DRAINING`.
In case the node starts draining the import should abort immediately by
throwing an `InterruptedException`.
was:
SS tables imports that have no chance of succeeding due to the node being
drained should fail fast.
In case there are any SS tables imports currently active, a draining node
should notify all of them upon flushing its column family stores.
Each notified SS tables import should abort as soon as possible by throwing an
`InterruptedException`.
> Node Draining Should Abort All Current SSTables Imports
> -------------------------------------------------------
>
> Key: CASSANDRA-18373
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18373
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Startup and Shutdown
> Reporter: Yuriy Semchyshyn
> Assignee: Yuriy Semchyshyn
> Priority: Normal
> Time Spent: 50m
> Remaining Estimate: 0h
>
> SS tables imports that will end up being ignored due to the node draining
> should fail instead of succeeding.
> Each active SS tables import should periodically check for the node status
> and see whether or not it is `DRAINING`.
> In case the node starts draining the import should abort immediately by
> throwing an `InterruptedException`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
