Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
riak_kv_pipe_get's failover has trouble with fast-input+slow-output rates #290
A problem was uncovered with
When the KV vnode that the pipe worker talks to returns an error, "not
This strategy does not work when the kvget workers are unable to keep
This bug manifests itself as MapReduce queries failing with a
One quick and incomplete fix may be to simply set the
One long-term fix is likely to change
Another long-term fix might be to alter the behavior of
Below is a basic method for reproducing the problem. The method is to
Below is the value captured in the
Recently I started to experience the same problem in Riak 1.1.2:
What value should I assign to 'q_limit'?
Should I modify it in ALL of the following files?
Is there any better solution available?
@tovbinm The default value for
Modifying the definition of
I do not know of a better solution at this time.
Sadly, no. The
Riak KV should expose setting the default queue limit per-phase-type basis in the app config, as well as setting it on a per-phase basis through the query definition in its MapReduce interface. Perhaps someone's eager to hack this for the next release?