# Confusion Regarding Unstable Bucket-ing in Kibana Visualizations **URL:** \ **Category:** Kibana\ **Created:** [January 26, 2018, 4:56pm UTC](https://discuss.elastic.co/t/confusion-regarding-unstable-bucket-ing-in-kibana-visualizations/117237 "2018-01-26T16:56:03Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\ **Post date:** [January 29, 2018, 4:00pm UTC](https://discuss.elastic.co/t/confusion-regarding-unstable-bucket-ing-in-kibana-visualizations/117237/5 "2018-01-29T16:00:06Z")
Here's another similar post; > [@Average value change when filtering or changing size](https://discuss.elastic.co/t/average-value-change-when-filtering-or-changing-size/107587/2): > > This sounds like the effect of merging the results from independent shards into a single response, which is generally considered an approximation and with smaller result sizes (when compared to the cardinality) can sometimes result in inaccurate results. Check out [https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-terms-aggregation.html#\_shard\_size\_3](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-terms-aggregation.html#_shard_size_3) I suggest using the shard\_size parameter in your terms aggregation to ensure that it pulls back enough ter… I got an error when I tried shard\_size:0 (thinking 0 makes it max out somehow?), but seems to work if I set it large. Give that a try and see if you get the correct counts with it. Looks like this; ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/e/1eb377777f55564589e6da4c36b7cfeff7b8ca75.png) --- _[View the full topic](https://discuss.elastic.co/t/confusion-regarding-unstable-bucket-ing-in-kibana-visualizations/117237)._