You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jason Brown (JIRA)" <ji...@apache.org> on 2015/07/25 01:29:04 UTC
[jira] [Comment Edited] (CASSANDRA-9896) Add ability to disable
commitlog recycling
[ https://issues.apache.org/jira/browse/CASSANDRA-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641199#comment-14641199 ]
Jason Brown edited comment on CASSANDRA-9896 at 7/24/15 11:28 PM:
------------------------------------------------------------------
I agree with [~brandon.williams] - if there's a reasonable workaround (that we can set as defaults in the yaml), let's go with that path for 2.1, which is (hopefully) starting to mature. To be clear, I'd like to chuck the commitlog recycling as far and as fast as we can, but it's at least stable(-ish) for now.
[~benedict] does the data [~brandon.williams] provide satisfy the problems you are seeing?
Update: I'd be reasonably ok with disabling the recycling as it should be not too invasive code-wise (apologies, I somehow interpreted the title of the ticket to remove the recycling).
was (Author: jasobrown):
I agree with [~brandon.williams] - if there's a reasonable workaround (that we can set as defaults in the yaml), let's go with that path for 2.1, which is (hopefully) starting to mature. To be clear, I'd like to chuck the commitlog recycling as far and as fast as we can, but it's at least stable(-ish) for now.
[~benedict] does the data [~brandon.williams] provide satisfy the problems you are seeing?
> Add ability to disable commitlog recycling
> ------------------------------------------
>
> Key: CASSANDRA-9896
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9896
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Brandon Williams
> Assignee: Benedict
> Fix For: 2.1.x
>
>
> See CASSANDRA-9533 for background, specifically the graphs I linked. Benedict suggests this is due the commitlog recycling and I agree, so the simplest solution is to be able to disable that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)