# Elastic shards

**URL:** <https://discuss.elastic.co/t/elastic-shards/168106>\
**Category:** Elasticsearch\
**Created:** [February 12, 2019, 7:51pm UTC](https://discuss.elastic.co/t/elastic-shards/168106 "2019-02-12T19:51:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mysterious\_Ze](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@Mysterious\_Ze](https://discuss.elastic.co/u/Mysterious_Ze)\
**Post date:** [February 12, 2019, 7:51pm UTC](https://discuss.elastic.co/t/elastic-shards/168106/1 "2019-02-12T19:51:45Z")

</div>

Hello  
After installing an elk stack with all configs as default and creating our dashboards, we are experiencing 2 major issues:

1. elastic does not work while reaching 95% of disk space. Is there any fine tuning regarding disk usage?

2. we frequently observe errors like 3 out 24 shards failed. What could be the issues and how to solve it ?

Any other fine tuning of the elk is also welcome 🙂

Thanks

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 12, 2019, 8:08pm UTC](https://discuss.elastic.co/t/elastic-shards/168106/2 "2019-02-12T20:08:50Z")

</div>

> [@Mysterious\_Ze](#):
>
> elastic does not work while reaching 95% of disk space. Is there any fine tuning regarding disk usage?

_Nothing_ works when the disk is 100% full, and 95% is almost 100%, so this is not totally unreasonable. Running out of disk space is a Very Bad Thing™ and the [disk-based shard allocator](https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html) is there to protect you from the consequences of that. You can adjust its settings if truly needed, but it's preferable to buy more disk space.

> [@Mysterious\_Ze](#):
>
> we frequently observe errors like 3 out 24 shards failed. What could be the issues and how to solve it ?

You will need to look at the Elasticsearch logs to find more information about this. If you need help interpreting them, please share them here and we'll do our best.

---

<div class="post-metadata">

**Author:** ![Mysterious\_Ze](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@Mysterious\_Ze](https://discuss.elastic.co/u/Mysterious_Ze)\
**Post date:** [February 13, 2019, 5:11pm UTC](https://discuss.elastic.co/t/elastic-shards/168106/3 "2019-02-13T17:11:15Z")

</div>

Thanks David  
I will look through the logs and revert back.

Regarding disk space, is there any fine tuning regarding shards or indices which could help to reduce the consumption of elastic?

Thanks

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 13, 2019, 5:42pm UTC](https://discuss.elastic.co/t/elastic-shards/168106/4 "2019-02-13T17:42:52Z")

</div>

Yes, there are some tips for tuning for disk usage in the [reference documentation](https://www.elastic.co/guide/en/elasticsearch/reference/6.6/tune-for-disk-usage.html).

---

<div class="post-metadata">

**Author:** ![Mysterious\_Ze](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@Mysterious\_Ze](https://discuss.elastic.co/u/Mysterious_Ze)\
**Post date:** [February 13, 2019, 5:47pm UTC](https://discuss.elastic.co/t/elastic-shards/168106/5 "2019-02-13T17:47:33Z")

</div>

Excellent David  
Thanks a lot 🙂

---

<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:** [March 13, 2019, 5:47pm UTC](https://discuss.elastic.co/t/elastic-shards/168106/6 "2019-03-13T17:47:33Z")

</div>

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