On Wed, Jun 22, 2011 at 4:35 PM, mcasandra <mohitanch...@gmail.com> wrote:
> might be helpful which varies from env to env. That's why I suggest look at
> the comments in cassandra.yaml and see which are applicable in your
> scenario. I learn something new everytime I read it.
>
Yep, and this was awesome - thanks very much for the reply - very helpful.
> BTW: Can you be clear as to what kind of recommendations are you referring
> to? NetworkToplogy, how many copies to store, uptime, load balancing,
> request routing when on DC is down? If you ask specific questions you might
> get better response.
Yes, this was my fault in not being specific, but I intentionally left it
open to see if anyone wanted to bring up something specific to their
environment that they thought would be valuable ('e.g. when our nodes got to
95% memory utilization, we find that GC behavior is doing X. Setting the JVM
option of 'foo' helped us reduce problem Y').
I was mainly looking initially for what folks thought were satisfactory
initial JVM/GC and *nix OS settings for a production node (e.g. 8 cores w/
64 gig ram, or an EC2 'large' or 'XL' node). E.g. what collector was used,
and why, whether folks have used the standard CMS collector or if they've
tried the G1 collector and what settings made them happy after testing...
Those kinds of things. Call it a tiny 'case study' if you will. Network
topology I thought I'd leave for a whole 'nuther discussion :)
As an aside, I definitely plan to publish our actual JVM and OS settings and
operational procedures once we find a happy medium based on our application
in the event that it might help someone else.
Thanks again!
Les
