# Large aggregate (too\_many\_buckets\_exception)

**URL:** <https://discuss.elastic.co/t/large-aggregate-too-many-buckets-exception/189091>\
**Category:** Elasticsearch\
**Created:** [July 5, 2019, 11:51am UTC](https://discuss.elastic.co/t/large-aggregate-too-many-buckets-exception/189091 "2019-07-05T11:51:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [July 5, 2019, 12:38pm UTC](https://discuss.elastic.co/t/large-aggregate-too-many-buckets-exception/189091/2 "2019-07-05T12:38:37Z")

</div>

Hi Roel,

> [@rvanegmond](#):
>
> For me, used to SQL, this seems like a relatively easy question.

If you're used to putting everything on one machine then life certainly is easy. In a distributed system like most elasticsearch deployments, you have to deal with what we call the [FAB conundrum](https://discuss.elastic.co/t/background-count-in-significant-terms-not-consistent/55824/8) which means you have to pick a trade-off.

The trade offs come from physical limits (speeds of networks, RAM limitations etc) and there are various options. Try run [this wizard](https://plnkr.co/edit/iJSFP8eRrhC7l7Hx2XOL?p=preview) and see which option it leads you to and we can discuss further here.

---

_[View the full topic](https://discuss.elastic.co/t/large-aggregate-too-many-buckets-exception/189091)._