# Urgent - No shards assigning **URL:** \ **Category:** Elasticsearch\ **Created:** [March 5, 2014, 3:54pm UTC](https://discuss.elastic.co/t/urgent-no-shards-assigning/16174 "2014-03-05T15:54:10Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Aaron\_Troy](https://avatars.discourse-cdn.com/v4/letter/a/5e9695/32.png) [@Aaron\_Troy](https://discuss.elastic.co/u/Aaron_Troy)\ **Post date:** [March 5, 2014, 3:54pm UTC](https://discuss.elastic.co/t/urgent-no-shards-assigning/16174/1 "2014-03-05T15:54:10Z")
Hi all, I have a system set up with 12 nodes, 48 indexes, and 12 shards/index (I know that number is way too high). Anyways, I'm in the process of indexing all the data onto a new index with far less shards, but I wanted to keep the initial cluster up for existing users searching the data. Well, one of the nodes ran out of memory and locked the system up, so I did a /etc/init.d/elasticsearch restart to each node. When things came back up, none of the nodes would assigned. There's absolutely nothing in the log file. It just looks like a normal start-up. Any idea? Here's my elasticsearch.yml file: cluster.name: Odine node.name: "rap-es" path.data: /data/elasticsearch/data path.work: /data/elasticsearch/work path.logs: /data/elasticsearch/logs #discovery.zen.minimum\_master\_nodes: 5 #discovery.zen.ping.multicast.enabled: true discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["141.161.88.169:9300", "141.161.88.174:9300","141.161.88.175:9300","141.161.88.176:9300", "141.161.88.177:9300","141.161.88.178:9300","141.161.88.179:9300", "141.161.88.181:9300","141.161.88.182:9300","141.161.88.183:9300", "141.161.88.184:9300","141.161.88.185:9300","141.161.88.186:9300"] node.data: false -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8dc54ad9-8606-4793-80c4-fb295ad05a15%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8dc54ad9-8606-4793-80c4-fb295ad05a15%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [March 5, 2014, 4:03pm UTC](https://discuss.elastic.co/t/urgent-no-shards-assigning/16174/2 "2014-03-05T16:03:42Z")
Doesn't node.data: false mean don't put anydata on this node? Nik On Wed, Mar 5, 2014 at 10:54 AM, Aaron Troy [atoy3731@gmail.com](mailto:atoy3731@gmail.com) wrote: > Hi all, > > I have a system set up with 12 nodes, 48 indexes, and 12 shards/index (I > know that number is way too high). > > Anyways, I'm in the process of indexing all the data onto a new index with > far less shards, but I wanted to keep the initial cluster up for existing > users searching the data. Well, one of the nodes ran out of memory and > locked the system up, so I did a /etc/init.d/elasticsearch restart to each > node. When things came back up, none of the nodes would assigned. There's > absolutely nothing in the log file. It just looks like a normal start-up. > Any idea? > > Here's my elasticsearch.yml file: > > cluster.name: Odine > node.name: "rap-es" > path.data: /data/elasticsearch/data > path.work: /data/elasticsearch/work > path.logs: /data/elasticsearch/logs > #discovery.zen.minimum\_master\_nodes: 5 > #discovery.zen.ping.multicast.enabled: true > discovery.zen.ping.multicast.enabled: false > discovery.zen.ping.unicast.hosts: ["141.161.88.169:9300"," > 141.161.88.174:9300","141.161.88.175:9300","141.161.88.176:9300"," > 141.161.88.177:9300","141.161.88.178:9300","141.161.88.179:9300"," > 141.161.88.181:9300","141.161.88.182:9300","141.161.88.183:9300"," > 141.161.88.184:9300","141.161.88.185:9300","141.161.88.186:9300"] > > node.data: false > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/8dc54ad9-8606-4793-80c4-fb295ad05a15%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8dc54ad9-8606-4793-80c4-fb295ad05a15%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/8dc54ad9-8606-4793-80c4-fb295ad05a15%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/8dc54ad9-8606-4793-80c4-fb295ad05a15%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1uaDgJYVSfK16etEc4YOBJzgV%2B59pLqx5X827F7n\_t4Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1uaDgJYVSfK16etEc4YOBJzgV%2B59pLqx5X827F7n_t4Q%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:45am UTC](https://discuss.elastic.co/t/urgent-no-shards-assigning/16174/3 "2017-07-06T01:45:31Z")