Hi Fabrice and Yuri,
Thanks for your questions and answers.
From my point of view, it is now a common architecture to have 1 or more DC
for on line queries, and 1 DC for stats.
It is also very common (and recommended ?) to specify -pr option for
anti-entropy repair operations.
In my case, I
137GB would fairly easily fit in core memory on a single node these days:
so it seems a very low amount for a 27 node cluster..
Off the top of my head: would 99th percentile latency be improved by using
replication factor 5, assuming you are doing quorum operations..
Sent from my phone
On 1 Mar
Hi Tim,
On 03/01/2014 02:02 PM, Tim Wintle wrote:
137GB would fairly easily fit in core memory on a single node these
days: so it seems a very low amount for a 27 node cluster..
Note that we only have 4 GB of RAM per node, so only 1 GB of Cassandra
heap. Are you assuming large memory
The last time I checked as in v 2.0.0 counters did not work. Over a period
of time , the counters drift from the correct value. There were several
open issues and proposal to rewrite the counter implementation
Have you checked if all the issues with counters have been fixed ?
regards
On Fri,
The complete rewrite of counters in 2.1(which should address the counter
accuracy issues) will still have this limitation. Deleting and recreating
counters is not supported and will continue to not be supported.
-Tupshin
On Mar 1, 2014 5:13 PM, Manoj Khangaonkar khangaon...@gmail.com wrote:
