# Disk threshold

**URL:** https://discuss.elastic.co/t/disk-threshold/271414
**Category:** Elasticsearch
**Created:** [April 27, 2021, 4:40pm UTC](https://discuss.elastic.co/t/disk-threshold/271414 "2021-04-27T16:40:57Z")
**Posts on this page:** 1
**Showing post:** 6

<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: [May 3, 2021, 7:44am UTC](https://discuss.elastic.co/t/disk-threshold/271414/6 "2021-05-03T07:44:33Z")

</div>

> [@Abhishek\_Shinde](#):
>
> in a single-node cluster setup considering "one node one disk"

[Elsewhere](https://discuss.elastic.co/t/control-over-writing-data-to-a-specific-drive/271695/5) you are asking about a design in which you have multiple disks, and therefore multiple nodes, all running on a single host, so I think you don't have a single-node cluster as you claim here. In that case the watermarks all work as documented to move shards around to ensure that no node's disk gets too full.

---

_[View the full topic](https://discuss.elastic.co/t/disk-threshold/271414)._
