# Stuck in Initializing ES 2.3.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [August 30, 2016, 6:53pm UTC](https://discuss.elastic.co/t/stuck-in-initializing-es-2-3-0/59353 "2016-08-30T18:53:47Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![fernandozanini](https://avatars.discourse-cdn.com/v4/letter/f/258eb7/32.png) [@fernandozanini](https://discuss.elastic.co/u/fernandozanini)\ **Post date:** [August 30, 2016, 6:53pm UTC](https://discuss.elastic.co/t/stuck-in-initializing-es-2-3-0/59353/1 "2016-08-30T18:53:47Z")
Scenario: 1 master node, no data 3 data nodes About 10 million documents indexed. What happened: It was indexing when master cluster disk became full. So I deleted some files and restarted elasticsearch. Then documents disapeared and didnt show any active shards Elasticsearch cluster state : Red Versions: Elasticsearch : 2.3.0 Kibana : 4.5.1 Cluster health Log: #curl -s '[http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)' { "cluster\_name" : "index\_app", "status" : "red", "timed\_out" : false, "number\_of\_nodes" : 3, "number\_of\_data\_nodes" : 2, "active\_primary\_shards" : 0, "active\_shards" : 0, "relocating\_shards" : 0, "initializing\_shards" : 5, "unassigned\_shards" : 2, "delayed\_unassigned\_shards" : 0, "number\_of\_pending\_tasks" : 0, "number\_of\_in\_flight\_fetch" : 0, "task\_max\_waiting\_in\_queue\_millis" : 0, "active\_shards\_percent\_as\_number" : 0.0 } #curl -s '[http://localhost:9200/\_cat/shards](http://localhost:9200/_cat/shards)' .kibana 0 p UNASSIGNED .kibana 0 r UNASSIGNED vw-docs-prod 1 p INITIALIZING 10.XXX.X.XX3 node-4 vw-docs-prod 3 p INITIALIZING 10.XXX.X.XX3 node-4 vw-docs-prod 2 p INITIALIZING 10.XXX.X.XX2 node-3 vw-docs-prod 4 p INITIALIZING 10.XXX.X.XX3 node-4 vw-docs-prod 0 p INITIALIZING 10.XXX.X.XX2 node-3 #curl -s '[http://localhost:9200/\_cat/indices?v](http://localhost:9200/_cat/indices?v)' health status index pri rep docs.count docs.deleted store.size pri.store.size red open .kibana 1 1 red open vw-docs-prod 5 0 ################################################################# ##elasticsearch.yml (data nodes) [cluster.name](http://cluster.name): cluster\_prod [node.name](http://node.name): node-2 node.master: false node.data: true network.host: 10.XXX.XX.X11 network.bind\_host: 10.XXX.XX.X11 network.publish\_to: 10.XXX.XX.X11 index.number\_of\_shards: 5 index.number\_of\_replicas: 1 discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ['masternode.mydomain'] ################################################################# ########elasticsearch.yml (master node) [cluster.name](http://cluster.name): cluster\_prod [node.name](http://node.name): node-1-master node.master: true node.data: false network.host: 10.XXX.XX.7 network.bind\_host: 10.XXX.XX.7 network.publish\_to: 10.XXX.XX.7 index.number\_of\_shards: 5 index.number\_of\_replicas: 1 discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ['masternode.mydomain'] ################################################################# Is there any way to reconstruct or recover these indices? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 30, 2016, 10:53pm UTC](https://discuss.elastic.co/t/stuck-in-initializing-es-2-3-0/59353/2 "2016-08-30T22:53:32Z")
> [@fernandozanini](#): > > 1 master node, no data That's a **really** bad idea - [Important Configuration Changes | Elasticsearch: The Definitive Guide [2.x] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/2.x/important-configuration-changes.html#_minimum_master_nodes) > [@fernandozanini](#): > > I deleted some files and restarted elasticsearch. What files? ---
**Author:** ![fernandozanini](https://avatars.discourse-cdn.com/v4/letter/f/258eb7/32.png) [@fernandozanini](https://discuss.elastic.co/u/fernandozanini)\ **Post date:** [August 31, 2016, 2:40pm UTC](https://discuss.elastic.co/t/stuck-in-initializing-es-2-3-0/59353/3 "2016-08-31T14:40:29Z")
Deleted .tar.gz files, then mounted /opt/elasticsearch/logs on another partition to solve space problem. ---
**Author:** ![fernandozanini](https://avatars.discourse-cdn.com/v4/letter/f/258eb7/32.png) [@fernandozanini](https://discuss.elastic.co/u/fernandozanini)\ **Post date:** [August 31, 2016, 5:49pm UTC](https://discuss.elastic.co/t/stuck-in-initializing-es-2-3-0/59353/4 "2016-08-31T17:49:15Z")
Dont know why, but solved the problem. What I did: Changed from: 1 dedicated master + 3 data nodes to: 4 master + data Restarted ES of all nodes. Everything is ok now.. thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:23pm UTC](https://discuss.elastic.co/t/stuck-in-initializing-es-2-3-0/59353/5 "2017-07-05T22:23:31Z")