You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cassandra.apache.org by Todd Burruss <bb...@expedia.com> on 2012/01/14 22:20:27 UTC

update row_cache_provider only after restart

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.

I'm using 1.0.6

Re: update row_cache_provider only after restart

Posted by Todd Burruss <bb...@expedia.com>.

https://issues.apache.org/jira/browse/CASSANDRA-3746


On 1/14/12 1:38 PM, "Jonathan Ellis" <jb...@gmail.com> wrote:

>IMO that's a bug.
>
>On Sat, Jan 14, 2012 at 3:20 PM, Todd Burruss <bb...@expedia.com>
>wrote:
>> 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.
>>
>> I'm using 1.0.6
>>
>
>
>
>-- 
>Jonathan Ellis
>Project Chair, Apache Cassandra
>co-founder of DataStax, the source for professional Cassandra support
>http://www.datastax.com

Re: update row_cache_provider only after restart

Posted by Jonathan Ellis <jb...@gmail.com>.

IMO that's a bug.

On Sat, Jan 14, 2012 at 3:20 PM, Todd Burruss <bb...@expedia.com> wrote:
> 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.
>
> I'm using 1.0.6
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com