LevelDB compaction and timeouts

Matthew Von-Maszewski matthewv at basho.com
Tue Jan 8 08:00:25 EST 2013


Would appreciate some configuration info:

- what version of Riak are you running?

- would you copy/paste the eleveldb section of your app.config?

- how many vnodes and physical servers are you running?

- what is hardware? cpu, memory, disk arrays

- are you seeing the work "waiting" in your LOG files?

Not sure that the above info will lead to a solution.  But it is a start.


On Jan 7, 2013, at 8:08 PM, Parnell Springmeyer <ixmatus at gmail.com> wrote:

> I've had a few situations arise where one or two nodes (all it needs is
> one node) will begin a heavy compaction cycle (determined by using gstat
> + looking at leveldb LOG files) and ALL queries put through the cluster
> (it doesn't matter which node) return a timeout.
> I can fix this situation by killing the node(s) in question then marking
> them as down; but the minute I bring them up the take everything down
> again until they complete.
> Is there a process by which I can keep queries being issued to certain
> nodes while having them live and dealing with their compaction? It seems
> highly inconvenient that I have to pick some time at night to bring them
> up so my users experience as few of the timeout errors are possible...
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

More information about the riak-users mailing list