# Cluster routing allocation decider preventing allocation **URL:** \ **Category:** Elasticsearch\ **Created:** [February 20, 2019, 3:48pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-decider-preventing-allocation/169249 "2019-02-20T15:48:12Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![deepakamritsar123](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@deepakamritsar123](https://discuss.elastic.co/u/deepakamritsar123)\ **Post date:** [February 20, 2019, 3:48pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-decider-preventing-allocation/169249/1 "2019-02-20T15:48:12Z")
I have 3 ElasticSearch servers in the cluster. Out of three, two are working normally and one server behaving strange. One server have no shard on it. When i restart the elasticsearch service or reboot the server, it is giving me the below error: [WARN][cluster.routing.allocation.decider] [testing\_node] after allocating, node [testing\_node] would have less than the required 0b free bytes threshold (-22254411079 bytes free), preventing allocation Although i have almost 98% free disk space on the server ---
**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 20, 2019, 10:11pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-decider-preventing-allocation/169249/2 "2019-02-20T22:11:12Z")
Hmm, weird. First up, there's a display bug that was fixed in [#33641](https://github.com/elastic/elasticsearch/pull/33641) (v6.5.0). The number reported (negative 22GB) is coming from the calculated disk space _minus_ the estimated size of the shard. In ≥ 6.5.0 we show these two numbers separately which is a bit more useful. From this message it's not clear if it's estimating the size of the disk as too small or the size of the shard as too large. Still, this seems unexpected. If you do this... ```auto POST _cluster/settings {"persistent":{"logger.org.elasticsearch.cluster.routing.allocation.decider":"TRACE"}} ``` ... then you should get copious logs from the allocator that might shed more light on what's going on. Reset this to normal with this... ```auto POST _cluster/settings {"persistent":{"logger.org.elasticsearch.cluster.routing.allocation.decider":null}} ``` ---
**Author:** ![deepakamritsar123](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@deepakamritsar123](https://discuss.elastic.co/u/deepakamritsar123)\ **Post date:** [February 21, 2019, 1:01pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-decider-preventing-allocation/169249/3 "2019-02-21T13:01:23Z")
Thank you David, for your guidance. It started working now. I ran the above command and checked the log file. Nothing was logged. Then I checked the \_cluster/health?pretty and it was showing me "relocating\_shards" : 2. I'm pretty sure that only running the above command haven't fixed my issue. ---
**Author:** ![deepakamritsar123](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@deepakamritsar123](https://discuss.elastic.co/u/deepakamritsar123)\ **Post date:** [February 21, 2019, 1:21pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-decider-preventing-allocation/169249/4 "2019-02-21T13:21:25Z")
Hi David, I'm not able to reset it. when i run the command: POST \_cluster/settings {"persistent":{"logger.org.elasticsearch.cluster.routing.allocation.decider":null}} it is giving me below error: {"error":{"root\_cause":[{"type":"action\_request\_validation\_exception","reason":"Validation Failed: 1: no settings to update;"}],"type":"action\_request\_validation\_exception","reason":"Validation Failed: 1: no settings to update;"},"status":400} ---
**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 21, 2019, 1:36pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-decider-preventing-allocation/169249/5 "2019-02-21T13:36:05Z")
> [@deepakamritsar123](#): > > I'm not able to reset it. when i run the command: Apologies, I mean `PUT` rather than `POST`. What version are you using? ---
**Author:** ![deepakamritsar123](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@deepakamritsar123](https://discuss.elastic.co/u/deepakamritsar123)\ **Post date:** [February 21, 2019, 4:31pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-decider-preventing-allocation/169249/6 "2019-02-21T16:31:40Z")
Tried PUT as well, no success **Request** curl -XPUT localhost:9200/\_cluster/settings -d '{"persistent":{"logger.org.elasticsearch.cluster.routing.allocation.decider":null}}' **Response:** {"error":{"root\_cause":[{"type":"action\_request\_validation\_exception","reason":"Validation Failed: 1: no settings to update;"}],"type":"action\_request\_validation\_exception","reason":"Validation Failed: 1: no settings to update;"},"status":400} **ES version** is 2.3.3 ---
**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 21, 2019, 5:35pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-decider-preventing-allocation/169249/7 "2019-02-21T17:35:13Z")
> [@deepakamritsar123](#): > > **ES version** is 2.3.3 Ohhhh. That's very old. It went [end-of-life](https://www.elastic.co/support/eol) in September 2017. I don't have access to a development environment in which I can dig into the problem you're facing, but it could well be addressed in a more recent version. I recommend upgrading. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 21, 2019, 5:35pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-decider-preventing-allocation/169249/8 "2019-03-21T17:35:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.