cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3746) updating row_cache_provider does not take affect until after a node is restarted
Date Tue, 24 Jan 2012 17:34:40 GMT

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

Jonathan Ellis commented on CASSANDRA-3746:
-------------------------------------------

Took a quick look at this -- the problem is that ColumnFamilyStore assumes that the cache
object won't change.  We can do capacity changes in-place like that but not implementation
replacement.
                
> updating row_cache_provider does not take affect until after a node is restarted
> --------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3746
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3746
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: B. Todd Burruss
>
> using CLI to update row_cache_provider does not take affect until after a node is restarted,
even though "describe" shows it as set.  not sure if you consider this a bug, but has caused
me some grief with my testing of providers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message