Tim Starling wrote:
I should add, queueing would be an appropriate response to cluster-wide
lag times of up to a few seconds. The request could be queued until a
slave with zero lag time becomes available. Serving an error message
only becomes appropriate when the expected queueing time is long enough
that the user would want an explanation.
Personally, I would think that serving an error message only becomes
appropriate when there is an error. Extreme slowness is not an error.
I would prefer for a request to take half an hour to complete than to
have to reload every five minutes for half an hour, and the request
still hasn't completed because it keeps timing out.
Timwi