Last modified: 2014-03-04 17:03:33 UTC
We currently only have timeouts for updates but we'll need to add them for searches because bad nodes can take out the whole clusters if they sit on the request, say, because they have bad heap settings. We'll need to set the shard timeout as well so Elasticsearch can timeout those requests. It is much better for Elasticsearch to timeout the requests because we'll get partial data and, if we timeout and just hit it again, then we can fill its request queues.
Looks like this is what we need on the Elasticsearch side: timeout A search timeout, bounding the search request to be executed within the specified time value and bail with the hits accumulated up to that point when expired. Defaults to no timeout.
Change 116481 had a related patch set uploaded by Manybubbles: Introduce search timeouts https://gerrit.wikimedia.org/r/116481
Change 116481 merged by jenkins-bot: Introduce search timeouts https://gerrit.wikimedia.org/r/116481
Change 116757 had a related patch set uploaded by Manybubbles: Introduce search timeouts https://gerrit.wikimedia.org/r/116757
Change 116757 merged by jenkins-bot: Introduce search timeouts https://gerrit.wikimedia.org/r/116757
