He probably meant in production. When playing around, and if you only have 2 nodes, you can set it to 2.
From memory RF of 2 means the Quorum is also 2, so you cannot afford to lose one. Thats fine for playing.
Aaron
On 15 Feb, 2011,at 01:51 PM, mcasandra <mohitanch...@gmail.com> wrote:
mcasandra wrote:
>
> In earlier post same thread you mentioned that replication factor should
> be set to less than N.
>
> Currently I am testing on 2 node cluster and I was able to set
> replication_factor to 2 (=N) and also when I did cfstats (I don't quite
> understand cfstats in detail) and see some activity on both nodes now
>
> [default@twissandra] update keyspace twissandra with replication_factor=2;
> 3ed6b708-389b-11e0-993f-b7fa7ed61af9
> [default@twissandra] set users['b']['add']='111';
> Value inserted.
>
> On the other node when I ran nodetool with -h as localhost, I see:
>
>
> Column Family: users
> SSTable count: 0
> Space used (live): 0
> Space used (total): 0
> Memtable Columns Count: 2
> Memtable Data Size: 52
> Memtable Switch Count: 0
> Read Count: 3
> Read Latency: NaN ms.
> Write Count: 2
> Write Latency: NaN ms.
> Pending Tasks: 0
> Key cache capacity: 200000
> Key cache size: 0
> Key cache hit rate: NaN
> Row cache: disabled
> Compacted row minimum size: 0
> Compacted row maximum size: 0
> Compacted row mean size: 0
>
>
Sorry I meant to say someone (Matthew Dennis) on the thread mentioned that
replication factor should be less than no. of nodes.
--
View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Internal-error-processing-insert-tp6025740p6025882.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
