Hi List, Fred,
After a week of going cross-eyed looking at stats & trying to engineer a
test case to make this happen in the test env I think I've made a
breakthrough.
We have a low but steady level of riak traffic but our application level
actions that result in solr reads are actually fairly in
Hi Fred,
Thanks for taking the time!
Yes, I noticed that unbalance yesterday when writing, looked into it after
sending and found our config is corrupt with one node ommitted and another
in there twice.
But, with such low traffic levels and the spikes being on the non-favoured
node I'm not current
It's pretty strange that you are seeing no search latency measurements on node
5. Are you sure your round robining is working? Are you favoring node 1?
In general, I don't think which node you hit for query should make a
difference, but I'd have to stare at the code some to be sure. In essenc
Hi List,
We have a standard riak cluster with 5 nodes and at the minute the traffic
levels are fairly low. Each of our application nodes has 25 client
connections, 5 to each riak node which get selected in a round robin.
Our application level requests involve multiple riak requests so our
traffic
