# Elasticsearch does not allocate shards to one node **URL:** \ **Category:** Elasticsearch\ **Created:** [January 21, 2019, 5:54am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-allocate-shards-to-one-node/164978 "2019-01-21T05:54:39Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\ **Post date:** [January 21, 2019, 5:54am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-allocate-shards-to-one-node/164978/1 "2019-01-21T05:54:39Z")
Hi All, I have a 3 node cluster of Elasticsearch. Somehow the system does not allocate any shards to node 2 (node 1 holds 34 and node 3 holds 31 shards). I'm using ES 6.1.2. elasticsearch.yml (from node 2) > cluster.name: abc-cluster > node.name: elasticsearch-node-2 > path.data: /home/abc/elasticsearch/elasticsearch\_data > path.logs: /home/abc/elasticsearch/elasticsearch\_logs > network.host: _site_ > discovery.zen.ping.unicast.hosts: ["elastic-01.abc.local", "elastic-03.abc.local"] > discovery.zen.minimum\_master\_nodes: 2 > xpack.security: > authc: > realms: > native: > type: native > order: 1 > custom: > type: custom > order: 0 > xpack.ssl.keystore.path: certs/elastic-certificates.p12 > xpack.ssl.truststore.path: certs/elastic-certificates.p12 > xpack.security.transport.ssl.enabled: true > xpack.security.transport.ssl.verification\_mode: certificate > path.repo: /home/abc/elasticsearch/elasticsearch\_snapshots What should I check? Thanks ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 21, 2019, 7:25am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-allocate-shards-to-one-node/164978/2 "2019-01-21T07:25:37Z")
One thing that can cause this is if the Elasticsearch version on the node not receiving any data is not exactly the same as the other nodes. That is what I would check first. If they are the same you should check logs and make sure the node has sufficient disk space. ---
**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\ **Post date:** [January 21, 2019, 7:38am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-allocate-shards-to-one-node/164978/3 "2019-01-21T07:38:16Z")
I can see nothing relevant in the log file. On the monitoring page of Kibana I can see there are 21.1 GB free space on node-2. So, that is why I'm a bit confused. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 21, 2019, 7:41am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-allocate-shards-to-one-node/164978/4 "2019-01-21T07:41:46Z")
Do all the nodes have the same amount of disk space allocated? ---
**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\ **Post date:** [January 21, 2019, 7:57am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-allocate-shards-to-one-node/164978/5 "2019-01-21T07:57:31Z")
I have found the issue. Node-2 and Node-3 are used for other purposes also - so plenty of disk space is used. I had to change the following params: cluster.routing.allocation.disk.watermark.low: "5Gb" cluster.routing.allocation.disk.watermark.high: "2Gb" cluster.routing.allocation.disk.watermark.flood\_stage: "1Gb" It is working now! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 18, 2019, 7:57am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-allocate-shards-to-one-node/164978/6 "2019-02-18T07:57:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.