cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13123) Draining a node might fail to delete all inactive commitlogs
Date Thu, 26 Oct 2017 18:07:00 GMT

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

Blake Eggleston commented on CASSANDRA-13123:
---------------------------------------------

I don't think these 2 tests can be in the same test class without being run in a specific
order. {{testCompressedCommitLogBackpressure}} needs it's byteman rules setup before the commit
log is started. So if {{testShutdownWithPendingTasks}} sets up it's schema and successfully
runs first, the other will hang.

I have a branch where each test is in it's own class [here|https://github.com/bdeggleston/cassandra/tree/13123-fix-3.0],
let me know if there are any objections

> 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
>            Assignee: Jan Urbański
>             Fix For: 3.0.16, 3.11.2, 4.0
>
>         Attachments: 13123-2.2.8.txt, 13123-3.0.10.txt, 13123-3.9.txt, 13123-trunk.txt
>
>
> 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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message