# Default shard allocation alogorithm **URL:** \ **Category:** Elasticsearch\ **Created:** [March 9, 2016, 6:12pm UTC](https://discuss.elastic.co/t/default-shard-allocation-alogorithm/43927 "2016-03-09T18:12:45Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Brandon\_Metcalf](https://avatars.discourse-cdn.com/v4/letter/b/8e7dd6/32.png) [@Brandon\_Metcalf](https://discuss.elastic.co/u/Brandon_Metcalf)\ **Post date:** [March 9, 2016, 6:12pm UTC](https://discuss.elastic.co/t/default-shard-allocation-alogorithm/43927/1 "2016-03-09T18:12:45Z")
In elasticsearch 1.5.2, is EvenShardsCountAllocator still the default allocation algorithm? We are seeing shards allocated based on disk utilization for clusters using the AWS Elasticsearch service. I have no idea what AWS is using, but hoping someone might be able to shed some light on this. An example, shards disk.used disk.avail disk.total disk.percent host ip node 0 122.5mb 6.7gb 6.8gb 1 x.x.x.x Perfection 332 951.3mb 28.5gb 29.5gb 3 x.x.x.x Mekano 332 1.1gb 28.3gb 29.5gb 3 x.x.x.x Slyde 0 122.4mb 6.7gb 6.8gb 1 x.x.x.x Hybrid II 0 122.4mb 6.7gb 6.8gb 1 x.x.x.x The Symbiote 664 1.9gb 27.6gb 29.5gb 6 x.x.x.x Karl Malus The three data nodes here have an even distribution of disk usage, but not shard count. Thanks. ---
**Author:** ![Brandon\_Metcalf](https://avatars.discourse-cdn.com/v4/letter/b/8e7dd6/32.png) [@Brandon\_Metcalf](https://discuss.elastic.co/u/Brandon_Metcalf)\ **Post date:** [March 9, 2016, 7:19pm UTC](https://discuss.elastic.co/t/default-shard-allocation-alogorithm/43927/2 "2016-03-09T19:19:21Z")
I was looking at the wrong column and it appears even disk usage is not evenly distributed. But, my question still stands; why would shards or disk usage not be evenly distributed? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:09pm UTC](https://discuss.elastic.co/t/default-shard-allocation-alogorithm/43927/3 "2017-07-05T23:09:48Z")