Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 24 Aug 2015 15:53:46 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12699433.1394205042000.146957.1440431626361@Atlassian.JIRA>
In-Reply-To: <JIRA.12699433.1394205042000@Atlassian.JIRA>
References: <JIRA.12699433.1394205042000@Atlassian.JIRA>
 <JIRA.12699433.1394205042055@arcas>
Subject: [jira] [Updated] (CASSANDRA-6819) The command "nodetool
 setcompactionthroughput" sometimes takes a long time to take effect
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-6819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-6819:
--------------------------------------
    Fix Version/s:     (was: 2.0.x)
                   3.x

> The command "nodetool setcompactionthroughput" sometimes takes a long time to take effect
> -----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6819
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6819
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Steven Lowenthal
>             Fix For: 3.x
>
>
> It's often necessary to throttle a large compaction.   When the nodetool setcompactionthroughput command is issued, the setting doesn't seem to take hold until another compaction starts, which may be some time on a bungled node.   This command should take hold immediately.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)