[jira] [Updated] (CASSANDRA-13123) Draining a node might fail to delete all inactive commitlogs
[ https://issues.apache.org/jira/browse/CASSANDRA-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Urbański updated CASSANDRA-13123: - Reproduced In: 3.0.10, 2.2.8 (was: 2.2.8, 3.0.10) Status: Patch Available (was: Open) > 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 > > 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.3.4#6332)
[jira] [Updated] (CASSANDRA-13123) Draining a node might fail to delete all inactive commitlogs
[ https://issues.apache.org/jira/browse/CASSANDRA-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Urbański updated CASSANDRA-13123: - Attachment: 13123-trunk.txt 13123-3.9.txt 13123-3.0.10.txt 13123-2.2.8.txt Patches for 2.2.8 and 3.0.10 and test-only patches for 3.9 and trunk > 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 > > 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.3.4#6332)
[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)
[jira] [Updated] (CASSANDRA-13092) Debian package does not install the hostpot_compiler command file
[
https://issues.apache.org/jira/browse/CASSANDRA-13092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Urbański updated CASSANDRA-13092:
-
Status: Patch Available (was: Open)
> Debian package does not install the hostpot_compiler command file
> -
>
> Key: CASSANDRA-13092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13092
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
>Reporter: Jan Urbański
>Priority: Trivial
> Labels: debian, patch
> Attachments: install-jit-compiler-command-file-in-Debian-package.patch
>
>
> The default {{cassandra-env.sh}} file sets a JIT compiler commands file via
> {{-XX:CompileCommandFile=$CASSANDRA_CONF/hotspot_compiler}} but the Debian
> package does not install that file, even though it's generated during the
> build process.
> Trivial patch against trunk attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
