Salman -
Please use "reply all" to include the mailing list in the discussion.
This is the first time you have mentioned a "failed server". Can you
go into more detail? How many servers are in this cluster?
--
Luke Bakken
Engineer
lbak...@basho.com
On Mon, Jul 18, 2016 at 2:39 AM, Salman Khale
Hi Salman,
Please re-read the Riak CS instructions carefully. You *must* only
have one Stanchion service running in your entire cluster:
https://docs.basho.com/riak/cs/2.1.1/cookbooks/installing/#installing-stanchion-on-a-node
Based on your latest email, it sounds as though Stanchion is running
Hi Travis,
Could you go into detail about how you're coming up with 9GiB per
node? Is this from the output of the "free" command?
Bitcask uses the operating system's buffers for file operations, and
will happily use as much free ram as it can get to speed up
operations. However, the OS will use t
Hi Travis -
The calculation provided for bitcask memory consumption is only a
rough guideline. Using more memory than the calculation suggests is
normal and expected with Riak. As you increase load on this cluster
memory use may go up further as the operating system manges disk
operations and buff
Yes from the free command
[root@riak1 ~]# free -g
totalusedfree shared buff/cache available
Mem: 45 9 0 0 36 35
Swap:23 0 22
Or from top
PID USER PR NIVIRT
Yes, the reason I'm concerned is that we projected much lower memory usage
based on the calculations. We originally provisioned 2x the required memory
and it appears that this will not be enough.
Am I correct in that the top cmd's RES memory for the beam.smp command is the
memory being used b
Hello everyone,
I released version 2.5.5 of the Python client today. This fixes a
long-standing issue with multi-get and multi-put operations where the
thread pool did not shut down cleanly when the interpreter shuts down.
Remember to "close()" your RiakClient instances to ensure cleanup.
https:/
