Changing low/high water marks in CB 2.0 beta
Mon, 10/29/2012 - 09:32
Hi everyone,
We are trying to bump up the high and low water marks as the default settings leave a lot of RAM unused. Defaults appear to be 75% high, 60% low, of the RAM allocated to CB.
We bumped this up to 80% high, 70% low but interestingly enough it appears the process to do this (cbepctl) only modifies the local node. As a result we ended up with one node with the revised settings which led to all sorts of interesting temp_oom behaviours.
Anyhow, should this command not replicate to make all nodes updated to the same settings?
We can easily script doing this on each node, but this sort of feels like a bug.
Thanks
This isn't a bug and the script is intended to work this way. In a future release we plan on having these parameters editable through the rest api so that they can more easily be replicated through the cluster.