You may want to monitor
- node_put_fsm_rejected (and get, too) to if overload protection rejected
put or get requests
- node_put_fsm_active, node_put_fsm_active_60s (to see how many active put
requests are being served now and in the last minute) there is metrics for
get, too. A spike of those metr
Thanks for your reply.
We are. We sort of expected an anomaly in the object size, but there was none.
We found the root cause. It was a large number of additions to a single set.
It’s not clear to me which metric reveals that problem, but it appears as
though object size doesn’t.
Alex
> On J
Hi Alex -
Are you monitoring any of Riak's statistics? Specifically object size
and sibling count, though all of the stats are useful.
--
Luke Bakken
Engineer
lbak...@basho.com
On Tue, Jan 26, 2016 at 11:40 AM, Alex Wolfe wrote:
> We have a 5 node Riak cluster running 2.1.1. This morning FSM Ti
