# 2.3.2 Java client : is there any way to throttle an \_msearch request?

**URL:** <https://discuss.elastic.co/t/2-3-2-java-client-is-there-any-way-to-throttle-an-msearch-request/116690>\
**Category:** Elasticsearch\
**Created:** [January 23, 2018, 2:29pm UTC](https://discuss.elastic.co/t/2-3-2-java-client-is-there-any-way-to-throttle-an-msearch-request/116690 "2018-01-23T14:29:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrec](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mrec](https://discuss.elastic.co/u/mrec)\
**Post date:** [January 23, 2018, 2:29pm UTC](https://discuss.elastic.co/t/2-3-2-java-client-is-there-any-way-to-throttle-an-msearch-request/116690/1 "2018-01-23T14:29:27Z")

</div>

The 6.1 docs mention [`max_concurrent_searches`](https://www.elastic.co/guide/en/elasticsearch/reference/6.1/search-multi-search.html), but it's not in the 2.3 docs or in any version of the Java API that I can see.

We're looking at supporting potentially-very-large multisearches from users; it's OK for them to be slow, but we don't want them to kill performance or for normal (non-`_msearch`) searches, or have those searches rejected because of a full search queue. Do we have any options other than breaking into small batches on our side and living with the extra transport overhead?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 20, 2018, 2:29pm UTC](https://discuss.elastic.co/t/2-3-2-java-client-is-there-any-way-to-throttle-an-msearch-request/116690/2 "2018-02-20T14:29:34Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.