On Tue, Mar 20, 2012 at 11:35 AM, Asher Feldman <afeldman(a)wikimedia.org> wrote:
How do you feel about a switch to change that behavior
(maxlag - 1)? It
would be nice to be continue guiding developers towards throttling API
requests around maxlag without complicating schema migrations by requiring
config deployments before and after every db for this reason only.
That sounds
reasonable to me, what alternative behavior do you
propose? A flag that, when enabled, causes maxlag to use the 2nd
highest lag instead of the highest lag?
Roan