# Asynchronous search shard size dependency

**URL:** <https://forum.opensearch.org/t/asynchronous-search-shard-size-dependency/9363>\
**Category:** General Feedback\
**Tags:** all-clients, discuss\
**Created:** [April 23, 2022, 2:46am UTC](https://forum.opensearch.org/t/asynchronous-search-shard-size-dependency/9363 "2022-04-23T02:46:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![0penS3arch](https://avatars.discourse-cdn.com/v4/letter/0/85e7bf/32.png) [@0penS3arch](https://forum.opensearch.org/u/0penS3arch)\
**Post date:** [April 23, 2022, 2:46am UTC](https://forum.opensearch.org/t/asynchronous-search-shard-size-dependency/9363/1 "2022-04-23T02:46:35Z")

</div>

For a (synchronous) query aggregation my understanding is that results are limited by shard size (minus offset) and response fields are indicative of this.

My question is for OpenSearch **asynchronous\_search** feature, is aggregation query bounded by shard size ? or when the query is completed is it aggregating on total estimated matching records?

---

<div class="post-metadata">

**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\
**Post date:** [February 7, 2023, 1:10am UTC](https://forum.opensearch.org/t/asynchronous-search-shard-size-dependency/9363/2 "2023-02-07T01:10:50Z")

</div>