You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jan Urbański (JIRA)" <ji...@apache.org> on 2017/01/14 21:28:26 UTC
[jira] [Created] (CASSANDRA-13123) Draining a node might fail to
delete all inactive commitlogs
Jan Urbański created CASSANDRA-13123:
----------------------------------------
Summary: Draining a node might fail to delete all inactive commitlogs
Key: CASSANDRA-13123
URL: https://issues.apache.org/jira/browse/CASSANDRA-13123
Project: Cassandra
Issue Type: Bug
Components: Local Write-Read Paths
Reporter: Jan Urbański
Fix For: 3.8
After issuing a drain command, it's possible that not all of the inactive commitlogs are removed.
The drain command shuts down the CommitLog instance, which in turn shuts down the CommitLogSegmentManager. This has the effect of discarding any pending management tasks it might have, like the removal of inactive commitlogs.
This in turn leads to an excessive amount of commitlogs being left behind after a drain and a lengthy recovery after a restart. With a fleet of dozens of nodes, each of them leaving several GB of commitlogs after a drain and taking up to two minutes to recover them on restart, the additional time required to restart the entire fleet becomes noticeable.
This problem is not present in 3.x or trunk because of the CLSM rewrite done in CASSANDRA-8844.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)