cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Hermes (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2100) Restart required to change cache_save_period
Date Wed, 23 Feb 2011 23:57:38 GMT

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

Jon Hermes commented on CASSANDRA-2100:
---------------------------------------

I thought that UpdateColumnFamily.applyModels() called CFS.reload() in all cases, but that
only happens when the server is not in client mode.

CFMetaData.apply(avro CfDef) will need to call the update logic. Patch forthcoming.

> 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.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

        

Mime
View raw message