# High disk watermark Error while Running Elasticsearch
**URL:** https://discuss.elastic.co/t/high-disk-watermark-error-while-running-elasticsearch/58262
**Category:** Elasticsearch
**Created:** [August 17, 2016, 1:49pm UTC](https://discuss.elastic.co/t/high-disk-watermark-error-while-running-elasticsearch/58262 "2016-08-17T13:49:00Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@vivc](https://discuss.elastic.co/u/vivc)
#### Post date: [August 17, 2016, 1:49pm UTC](https://discuss.elastic.co/t/high-disk-watermark-error-while-running-elasticsearch/58262/1 "2016-08-17T13:49:00Z")
Getting the following error while running elastic search.
ussjvlx1128 [6:43] [/home/xvivech] -\> [2016-08-17 06:44:26,762][WARN][cluster.routing.allocation.decider] [Clea] high disk watermark [90%] exceeded on [ZlnSBDYcQPCxB\_RnggHtBg][Clea][/home/xvivech/log\_mgt/elasticsearch-2.0.0/data/elasticsearch/nodes/0] free: 507.8mb[9.9%], shards will be relocated away from this node
The elasticsearch API were working fine earlier but now getting the follow error
TRACE: 2016-08-17T12:42:16Z
-\> POST [http://147.117.52.29:9200/\_search/template?search\_type=count](http://147.117.52.29:9200/_search/template?search_type=count)
{
"file": "getchassis",
"params": {
"log\_type": true
}
}
\<- 503
{
"error": {
"root\_cause": [],
"type": "search\_phase\_execution\_exception",
"reason": "all shards failed",
"phase": "query",
"grouped": true,
"failed\_shards": []
},
"status": 503
}
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [August 17, 2016, 7:32pm UTC](https://discuss.elastic.co/t/high-disk-watermark-error-while-running-elasticsearch/58262/2 "2016-08-17T19:32:27Z")
I'd suggest that you have unallocated shards due to a full disk.
---
### Author:  [@wheels](https://discuss.elastic.co/u/wheels)
#### Post date: [August 18, 2016, 10:57pm UTC](https://discuss.elastic.co/t/high-disk-watermark-error-while-running-elasticsearch/58262/3 "2016-08-18T22:57:01Z")
I seem to be having a similar issue. Win2003 server that elastic was running on ran low on space, and due to a crash had to be forcefully restarted.
I have a cluster status of RED now with 9 unassigned shards.
radiology 4 p STARTED 434927 502.5mb 169.254.227.33 Wolf
radiology 4 r UNASSIGNED
radiology 0 p STARTED 434681 503.6mb 169.254.227.33 Wolf
radiology 0 r UNASSIGNED
radiology 3 p UNASSIGNED
radiology 3 r UNASSIGNED
radiology 1 p UNASSIGNED
radiology 1 r UNASSIGNED
radiology 2 p STARTED 434642 505.6mb 169.254.227.33 Wolf
radiology 2 r UNASSIGNED
.kibana 0 p UNASSIGNED
.kibana 0 r UNASSIGNED
I'm trying to assign these shards so the cluster will run again, but I'm struggling badly.
The reroute -d command runs, but never actaully moved a shard into the running state.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:26pm UTC](https://discuss.elastic.co/t/high-disk-watermark-error-while-running-elasticsearch/58262/4 "2017-07-05T22:26:50Z")