Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 25 Feb 2011 21:03:22 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <394564338.731.1298667802110.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <158412416.5981.1296683248987.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (CASSANDRA-2100) Restart required to change
 cache_save_period
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on CASSANDRA-2100:
-----------------------------------

Integrated in Cassandra-0.7 #324 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/324/])
    add [get|set][row|key]cacheSavePeriod to JMX
patch by Jon Hermes; reviewed by jbellis for CASSANDRA-2100


> Restart required to change cache_save_period
> --------------------------------------------
>
>                 Key: CASSANDRA-2100
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2100
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Nick Bailey
>            Assignee: Jon Hermes
>            Priority: Minor
>             Fix For: 0.7.3
>
>         Attachments: 2100-2.txt, 2100-3.txt, 2100.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The cache_save_period is set in the schema for each column family.  However this value is only checked when a node starts up so changing this value isn't really dynamic.
> We should actually change this when the schema changes instead of having to restart.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira