# Missing index issue in a cluster **URL:** \ **Category:** Elasticsearch\ **Tags:** es-hadoop\ **Created:** [July 31, 2017, 3:25pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210 "2017-07-31T15:25:31Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![aliyesami](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@aliyesami](https://discuss.elastic.co/u/aliyesami)\ **Post date:** [July 31, 2017, 3:25pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/1 "2017-07-31T15:25:32Z")
I have a 5 node cluster , what I noticed is that when I create the ES external table on node1 , the index is being created on node5 (where hive is not installed) , and then when I try to select from this table I get the error index missing . I know the index is there since I can select from it on node using curl . how can I make hive to create the index on node1 and not node5? > hive\> select \* from pa\_lane\_txn\_es ; > OK > Failed with exception java.io.IOException:org.elasticsearch.hadoop.EsHadoopIllegalArgumentException: Index [lane\_txn/txn\_id] missing and settings [es.index.read.missing.as.empty] is set to false > Time taken: 0.055 seconds > hive\> > > CREATE EXTERNAL TABLE pa\_lane\_txn\_es ( > txn\_id BIGINT, > txn\_process\_date TIMESTAMP, > transp\_id STRING, > ext\_plaza\_id STRING, > ext\_lane\_id STRING, > ext\_date\_time TIMESTAMP, > toll\_amt\_charged FLOAT, > toll\_amt\_collected FLOAT, > toll\_amt\_full FLOAT, > ent\_plaza\_id STRING,ent\_date\_time TIMESTAMP,ent\_lane\_id STRING) > STORED BY 'org.elasticsearch.hadoop.hive.EsStorageHandler' > TBLPROPERTIES( 'es.nodes.wan.only' = 'true','es.resource' = 'lane\_txn/txn\_id','es.mapping.id'='txn\_id'); > > [root@hadoop5 ~]# curl 'localhost:9200/\_cat/indices?v' > health status index uuid pri rep docs.count docs.deleted store.size pri.store.size > yellow open .kibana TE5kvKgeRx6mmU0x3kbN4g 1 1 2 0 8.5kb 8.5kb > yellow open lane\_txn WQRSyvgBSKqUiuBgRcfI2g 5 1 10 0 32kb 32kb > [root@hadoop5 ~]# ---
**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\ **Post date:** [July 31, 2017, 3:42pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/2 "2017-07-31T15:42:48Z")
The connector should be able to read data from the index on node 5 if it is indeed part of the elasticsearch cluster. Could you share your cluster setup (hive and Elasticsearch) as well as any failure logs from the hive workers/server? ---
**Author:** ![aliyesami](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@aliyesami](https://discuss.elastic.co/u/aliyesami)\ **Post date:** [July 31, 2017, 4:10pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/3 "2017-07-31T16:10:31Z")
I did not configure elasticsearch as cluster , I have a hadoop 5 node cluster running hortonworks. wanted to upload the logfiles but it wont let me . elasticsearch.yml file contents > cluster.name: elasticsearch > node.name: "node1" > node.master: true > node.data: true > path.data: /elastic/data > path.logs: /elastic/logs > network.host: 127.0.0.1 > http.port: 9200 tail -300 elasticsearch.log > [2017-07-31T10:23:36,608][WARN][o.e.b.JNANatives] unable to install syscall filter: > java.lang.UnsupportedOperationException: seccomp unavailable: CONFIG\_SECCOMP not compiled into kernel, CONFIG\_SECCOMP and CONFIG\_SECCOMP\_FILTER are needed > at org.elasticsearch.bootstrap.SystemCallFilter.linuxImpl(SystemCallFilter.java:363) ~[elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.SystemCallFilter.init(SystemCallFilter.java:638) ~[elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.JNANatives.tryInstallSystemCallFilter(JNANatives.java:215) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.Natives.tryInstallSystemCallFilter(Natives.java:99) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:111) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:194) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:351) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:123) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:114) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:67) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:122) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.cli.Command.main(Command.java:88) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91) [elasticsearch-5.5.0.jar:5.5.0] > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84) [elasticsearch-5.5.0.jar:5.5.0] > [2017-07-31T10:23:36,707][INFO][o.e.n.Node] [node1] initializing ... > [2017-07-31T10:23:36,762][INFO][o.e.e.NodeEnvironment] [node1] using [1] data paths, mounts [[/ (/dev/mapper/vg\_hadoop1-lv\_root)]], net usable\_space [12.3gb], net total\_space [49gb], spins? [possibly], types [ext4] > [2017-07-31T10:23:36,762][INFO][o.e.e.NodeEnvironment] [node1] heap size [1.9gb], compressed ordinary object pointers [true] > [2017-07-31T10:23:36,764][INFO][o.e.n.Node] [node1] node name [node1], node ID [foP4x5AWSJKBvq-yCSo4-A] > [2017-07-31T10:23:36,764][INFO][o.e.n.Node] [node1] version[5.5.0], pid[11538], build[260387d/2017-06-30T23:16:05.735Z], OS[Linux/2.6.32-642.6.2.el6.x86\_64/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0\_111/25.111-b15] > [2017-07-31T10:23:36,764][INFO][o.e.n.Node] [node1] JVM arguments [-Xms2g, -Xmx2g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+DisableExplicitGC, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutOfMemoryError, -Des.path.home=/usr/share/elasticsearch] > [2017-07-31T10:23:37,429][INFO][o.e.p.PluginsService] [node1] loaded module [aggs-matrix-stats] > [2017-07-31T10:23:37,429][INFO][o.e.p.PluginsService] [node1] loaded module [ingest-common] > [2017-07-31T10:23:37,429][INFO][o.e.p.PluginsService] [node1] loaded module [lang-expression] > [2017-07-31T10:23:37,429][INFO][o.e.p.PluginsService] [node1] loaded module [lang-groovy] > [2017-07-31T10:23:37,429][INFO][o.e.p.PluginsService] [node1] loaded module [lang-mustache] > [2017-07-31T10:23:37,429][INFO][o.e.p.PluginsService] [node1] loaded module [lang-painless] > [2017-07-31T10:23:37,429][INFO][o.e.p.PluginsService] [node1] loaded module [parent-join] > [2017-07-31T10:23:37,429][INFO][o.e.p.PluginsService] [node1] loaded module [percolator] > [2017-07-31T10:23:37,429][INFO][o.e.p.PluginsService] [node1] loaded module [reindex] > [2017-07-31T10:23:37,430][INFO][o.e.p.PluginsService] [node1] loaded module [transport-netty3] > [2017-07-31T10:23:37,430][INFO][o.e.p.PluginsService] [node1] loaded module [transport-netty4] > [2017-07-31T10:23:37,430][INFO][o.e.p.PluginsService] [node1] no plugins loaded > [2017-07-31T10:23:38,505][INFO][o.e.d.DiscoveryModule] [node1] using discovery type [zen] > [2017-07-31T10:23:38,908][INFO][o.e.n.Node] [node1] initialized > [2017-07-31T10:23:38,908][INFO][o.e.n.Node] [node1] starting ... > [2017-07-31T10:23:39,027][INFO][o.e.t.TransportService] [node1] publish\_address {127.0.0.1:9300}, bound\_addresses {127.0.0.1:9300} > [2017-07-31T10:23:39,036][WARN][o.e.b.BootstrapChecks] [node1] max number of threads [1024] for user [elasticsearch] is too low, increase to at least [2048] > [2017-07-31T10:23:39,037][WARN][o.e.b.BootstrapChecks] [node1] system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk > [2017-07-31T10:23:42,104][INFO][o.e.c.s.ClusterService] [node1] new\_master {node1}{foP4x5AWSJKBvq-yCSo4-A}{Q6Vtni35R0WfWr8rh\_LmPw}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined) > [2017-07-31T10:23:42,120][INFO][o.e.h.n.Netty4HttpServerTransport] [node1] publish\_address {127.0.0.1:9200}, bound\_addresses {127.0.0.1:9200} > [2017-07-31T10:23:42,120][INFO][o.e.n.Node] [node1] started > [2017-07-31T10:23:42,138][INFO][o.e.g.GatewayService] [node1] recovered [0] indices into cluster\_state ---
**Author:** ![aliyesami](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@aliyesami](https://discuss.elastic.co/u/aliyesami)\ **Post date:** [July 31, 2017, 4:23pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/4 "2017-07-31T16:23:17Z")
I don't know if this would be of any help. on node1 I commented out the clustername parameter . also noted that on node1 its not pulling up the indexes even though curl shows elasticsearch is up . on other nodes it does show the indexes. > [root@hadoop1 elasticsearch]# curl '127.0.0.1:9200/\_cat/indices?v' > health status index uuid pri rep docs.count docs.deleted store.size pri.store.size > > [root@hadoop1 elasticsearch]# curl 127.0.0.1:9200 > { > "name" : "node1", > "cluster\_name" : "elasticsearch", > "cluster\_uuid" : "T7Lvu\_xIRpmT4zBjdyKGBQ", > "version" : { > "number" : "5.5.0", > "build\_hash" : "260387d", > "build\_date" : "2017-06-30T23:16:05.735Z", > "build\_snapshot" : false, > "lucene\_version" : "6.6.0" > }, > "tagline" : "You Know, for Search" > } > [root@hadoop5 ~]# curl 'localhost:9200/\_cat/indices?v' > health status index uuid pri rep docs.count docs.deleted store.size pri.store.size > yellow open .kibana TE5kvKgeRx6mmU0x3kbN4g 1 1 2 0 8.5kb 8.5kb > yellow open lane\_txn VDSqRpIaTlKVBdNSuwIwYg 5 1 10 0 32kb 32kb > [root@hadoop5 ~]# > [root@hadoop3 ~]# curl 'localhost:9200/\_cat/indices?v' > health status index uuid pri rep docs.count docs.deleted store.size pri.store.size > yellow open .kibana -LYFpMNjRUmIHFiI24U18A 1 1 1 0 3.2kb 3.2kb > You have new mail in /var/spool/mail/root ---
**Author:** ![aliyesami](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@aliyesami](https://discuss.elastic.co/u/aliyesami)\ **Post date:** [July 31, 2017, 5:43pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/5 "2017-07-31T17:43:51Z")
I added this parameter to elasticsearch.yml on node1 but still I don't see its adding other nodes to the cluster and strangely enough it does create index on node5. > discovery.zen.ping.unicast.hosts: ["10.100.44.16", "10.100.44.17", "10.100.44.18", "10.100.44.19", "10.100.44.20"] ---
**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\ **Post date:** [August 1, 2017, 9:09pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/6 "2017-08-01T21:09:11Z")
Are you running a separate Elasticsearch node on each Hadoop node? You will need to configure the Elasticsearch nodes to form a cluster amongst themselves. If an index is created on node 5 and node 5 is not in a cluster with the other nodes, then those nodes will not be aware of the index created on node 5. ---
**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\ **Post date:** [August 1, 2017, 9:37pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/7 "2017-08-01T21:37:39Z")
@aliyesami Please follow the instructions [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/important-settings.html) on configuring Elasticsearch to run as a cluster. ---
**Author:** ![aliyesami](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@aliyesami](https://discuss.elastic.co/u/aliyesami)\ **Post date:** [August 2, 2017, 1:33pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/8 "2017-08-02T13:33:13Z")
hi James I followed the instructions best as I can and also tried to apply the info I found on web but the nodes are not discovering each other , please see my configuration files and the elastic log. > [root@hadoop1 ~]# cat /etc/elasticsearch/elasticsearch.yml > cluster.name: ftes > transport.host: 127.0.0.1 > http.host: 0.0.0.0 > network.bind\_host: "hadoop2,hadoop3,hadoop4,hadoop5" > network.publish\_host: _non\_loopback:ipv4_ > node.name: hadoop1 > node.master: true > node.data: true > path.data: /elastic/data > path.logs: /elastic/logs > network.host: hadoop1 > bootstrap.system\_call\_filter: false > discovery.zen.minimum\_master\_nodes: 3 > #discovery.zen.ping.unicast.hosts: ["10.100.44.16" ,"10.100.44.17" ,"10.100.44.18" ,"10.100.44.19" ,"10.100.44.20"] > discovery.zen.ping.unicast.hosts: ["hadoop1","hadoop2","hadoop3","hadoop4","hadoop5"] > > [root@hadoop2 ~]# cat /etc/elasticsearch/elasticsearch.yml > cluster.name: ftes > transport.host: 127.0.0.1 > http.host: 0.0.0.0 > network.bind\_host: "hadoop1,hadoop3,hadoop4,hadoop5" > network.publish\_host: _non\_loopback:ipv4_ > node.name: hadoop2 > node.master: true > node.data: true > path.data: /elastic/data > path.logs: /elastic/logs > network.host: hadoop2 > bootstrap.system\_call\_filter: false > discovery.zen.minimum\_master\_nodes: 3 > #discovery.zen.ping.unicast.hosts: ["10.100.44.16" ,"10.100.44.17" ,"10.100.44.18" ,"10.100.44.19" ,"10.100.44.20"] > discovery.zen.ping.unicast.hosts: ["hadoop1","hadoop2","hadoop3","hadoop4","hadoop5"] > > [root@hadoop3 ~]# cat /etc/elasticsearch/elasticsearch.yml > cluster.name: ftes > transport.host: 127.0.0.1 > http.host: 0.0.0.0 > network.bind\_host: "hadoop1,hadoop2,hadoop4,hadoop5" > network.publish\_host: _non\_loopback:ipv4_ > node.name: hadoop3 > node.master: true > node.data: true > path.data: /elastic/data > path.logs: /elastic/logs > network.host: hadoop3 > bootstrap.system\_call\_filter: false > discovery.zen.minimum\_master\_nodes: 3 > #discovery.zen.ping.unicast.hosts: ["10.100.44.16" ,"10.100.44.17" ,"10.100.44.18" ,"10.100.44.19" ,"10.100.44.20"] > discovery.zen.ping.unicast.hosts: ["hadoop1","hadoop2","hadoop3","hadoop4","hadoop5"] > > [root@hadoop4 ~]# cat /etc/elasticsearch/elasticsearch.yml > cluster.name: ftes > transport.host: 127.0.0.1 > http.host: 0.0.0.0 > network.bind\_host: "hadoop1,hadoop2,hadoop3,hadoop5" > network.publish\_host: _non\_loopback:ipv4_ > node.name: hadoop4 > node.master: true > node.data: true > path.data: /elastic/data > path.logs: /elastic/logs > network.host: hadoop4 > bootstrap.system\_call\_filter: false > discovery.zen.minimum\_master\_nodes: 3 > #discovery.zen.ping.unicast.hosts: ["10.100.44.16" ,"10.100.44.17" ,"10.100.44.18" ,"10.100.44.19" ,"10.100.44.20"] > discovery.zen.ping.unicast.hosts: ["hadoop1","hadoop2","hadoop3","hadoop4","hadoop5"] > > [root@hadoop5 ~]# cat /etc/elasticsearch/elasticsearch.yml > cluster.name: ftes > transport.host: 127.0.0.1 > http.host: 0.0.0.0 > network.bind\_host: "hadoop1,hadoop2,hadoop3,hadoop4" > network.publish\_host: _non\_loopback:ipv4_ > node.name: hadoop5 > node.master: true > node.data: true > path.data: /elastic/data > path.logs: /elastic/logs > network.host: hadoop5 > bootstrap.system\_call\_filter: false > discovery.zen.minimum\_master\_nodes: 3 > #discovery.zen.ping.unicast.hosts: ["10.100.44.16" ,"10.100.44.17" ,"10.100.44.18" ,"10.100.44.19" ,"10.100.44.20"] > discovery.zen.ping.unicast.hosts: ["hadoop1","hadoop2","hadoop3","hadoop4","hadoop5"] > [2017-08-02T09:11:22,652][INFO][o.e.n.Node] [hadoop1] initializing ... > [2017-08-02T09:11:22,730][INFO][o.e.e.NodeEnvironment] [hadoop1] using [1] data paths, mounts [[/ (/dev/mapper/vg\_hadoop1-lv\_root)]], net usable\_space [12gb], net total\_space [49gb], spins? [possibly], types [ext4] > [2017-08-02T09:11:22,731][INFO][o.e.e.NodeEnvironment] [hadoop1] heap size [1.9gb], compressed ordinary object pointers [true] > [2017-08-02T09:11:22,733][INFO][o.e.n.Node] [hadoop1] node name [hadoop1], node ID [sdZ-rxXISYuu4gkVf\_\_-mw] > [2017-08-02T09:11:22,733][INFO][o.e.n.Node] [hadoop1] version[5.5.0], pid[26216], build[260387d/2017-06-30T23:16:05.735Z], OS[Linux/2.6.32-642.6.2.el6.x86\_64/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0\_111/25.111-b15] > [2017-08-02T09:11:22,733][INFO][o.e.n.Node] [hadoop1] JVM arguments [-Xms2g, -Xmx2g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+DisableExplicitGC, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutOfMemoryError, -Des.path.home=/usr/share/elasticsearch] > [2017-08-02T09:11:23,502][INFO][o.e.p.PluginsService] [hadoop1] loaded module [aggs-matrix-stats] > [2017-08-02T09:11:23,502][INFO][o.e.p.PluginsService] [hadoop1] loaded module [ingest-common] > [2017-08-02T09:11:23,502][INFO][o.e.p.PluginsService] [hadoop1] loaded module [lang-expression] > [2017-08-02T09:11:23,502][INFO][o.e.p.PluginsService] [hadoop1] loaded module [lang-groovy] > [2017-08-02T09:11:23,502][INFO][o.e.p.PluginsService] [hadoop1] loaded module [lang-mustache] > [2017-08-02T09:11:23,502][INFO][o.e.p.PluginsService] [hadoop1] loaded module [parent-join] > [2017-08-02T09:11:23,503][INFO][o.e.p.PluginsService] [hadoop1] loaded module [percolator] > [2017-08-02T09:11:23,503][INFO][o.e.p.PluginsService] [hadoop1] loaded module [reindex] > [2017-08-02T09:11:23,503][INFO][o.e.p.PluginsService] [hadoop1] loaded module [transport-netty3] > [2017-08-02T09:11:23,503][INFO][o.e.p.PluginsService] [hadoop1] loaded module [transport-netty4] > [2017-08-02T09:11:23,503][INFO][o.e.p.PluginsService] [hadoop1] no plugins loaded > [2017-08-02T09:11:24,856][INFO][o.e.d.DiscoveryModule] [hadoop1] using discovery type [zen] > [2017-08-02T09:11:25,316][INFO][o.e.n.Node] [hadoop1] initialized > [2017-08-02T09:11:25,316][INFO][o.e.n.Node] [hadoop1] starting ... > [2017-08-02T09:11:25,460][INFO][o.e.t.TransportService] [hadoop1] publish\_address {127.0.0.1:9300}, bound\_addresses {127.0.0.1:9300} > [2017-08-02T09:11:25,471][WARN][o.e.b.BootstrapChecks] [hadoop1] max number of threads [1024] for user [elasticsearch] is too low, increase to at least [2048] > [2017-08-02T09:11:28,505][WARN][o.e.d.z.ZenDiscovery] [hadoop1] not enough master nodes discovered during pinging (found [[Candidate{node={hadoop1}{sdZ-rxXISYuu4gkVf\_\_-mw}{Q1\_mobLlTP6CHxHsbyICYA}{127.0.0.1}{127.0.0.1:9300}, clusterStateVersion=-1}]], but needed [3]), pinging again ---
**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\ **Post date:** [August 2, 2017, 5:33pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/9 "2017-08-02T17:33:10Z")
> [@aliyesami](#): > > transport.host: 127.0.0.1 > http.host: 0.0.0.0 > network.bind\_host: "hadoop2,hadoop3,hadoop4,hadoop5" > network.publish\_host: non\_loopback:ipv4 > ... > network.host: hadoop1 > ... > discovery.zen.ping.unicast.hosts: [“hadoop1”,“hadoop2”,“hadoop3”,“hadoop4”,“hadoop5”] I think your network settings need to be fixed up a little bit. In this case your `network.host` property should be fine (assuming `hadoop1` is a resolvable hostname). Your entries for `transport.host` and `http.host` are binding to local addresses. Those two settings normally default to whatever `network.host` is configured to. In setting them, you are overriding each network module to bind to the local address, causing the inability to communicate over the network. I would also remove the `network.bind_host` and `network.publish_host` since those do not seem to be correctly set either. The bind host setting is for telling the node which addresses to listen **on** , which should be the node's network addresses. The publish host setting is what the node uses to tell other nodes where they can reach it. These settings are here in the event that you are running Elasticsearch with a very particular network setup, and for most cases, they can be ignored. They will default to the value of `network.host` if unset. For more information on how the networking is configured in Elasticsearch, we have the general network settings documentation [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html), documentation about the transport level communication [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-transport.html), and documentation about the http level communication [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html). ---
**Author:** ![aliyesami](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@aliyesami](https://discuss.elastic.co/u/aliyesami)\ **Post date:** [August 2, 2017, 7:32pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/10 "2017-08-02T19:32:48Z")
what should i do with transport.host and http.host settings? hadoop1 to hadoop5 are not in DNS but resolvable via hosts file . and if i remove all the four parameters that you mentioned than Elasticsearch refuse to start even. > [elasticsearch@hadoop2 config]$ more elasticsearch.yml > cluster.name: ftes > node.name: hadoop2 > node.master: true > node.data: true > path.data: /elastic/data > path.logs: /elastic/logs > network.host: hadoop2 > bootstrap.system\_call\_filter: false > discovery.zen.minimum\_master\_nodes: 3 > #discovery.zen.ping.unicast.hosts: [“10.100.44.16” ,“10.100.44.17” ,“10.100.44.18” ,“10.100.44.19” ,“10.100.44.20”] > #discovery.zen.ping.unicast.hosts: [“hadoop1”,“hadoop2”,“hadoop3”,“hadoop4”,“hadoop5”] > [2017-08-02T16:14:38,411][INFO][o.e.p.PluginsService] [hadoop1] no plugins loaded > [2017-08-02T16:14:39,551][INFO][o.e.d.DiscoveryModule] [hadoop1] using discovery type [zen] > [2017-08-02T16:14:40,111][INFO][o.e.n.Node] [hadoop1] initialized > [2017-08-02T16:14:40,112][INFO][o.e.n.Node] [hadoop1] starting ... > [2017-08-02T16:14:40,241][INFO][o.e.t.TransportService] [hadoop1] publish\_address {10.100.44.17:9300}, bound\_addresses {10.100.44.17:9300} > [2017-08-02T16:14:40,250][INFO][o.e.b.BootstrapChecks] [hadoop1] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks > [2017-08-02T16:14:40,251][ERROR][o.e.b.Bootstrap] [hadoop1] node validation exception > [1] bootstrap checks failed > [1]: max number of threads [1024] for user [elasticsearch] is too low, increase to at least [2048] > [2017-08-02T16:14:40,253][INFO][o.e.n.Node] [hadoop1] stopping ... > [2017-08-02T16:14:40,316][INFO][o.e.n.Node] [hadoop1] stopped > [2017-08-02T16:14:40,316][INFO][o.e.n.Node] [hadoop1] closing ... > [2017-08-02T16:14:40,326][INFO][o.e.n.Node] [hadoop1] closed > [elasticsearch@hadoop1 config]$ did more tests and narrowed it down to this parameter , without this parameter the elasticsearch is not starting . > transport.host: 127.0.0.1 ---
**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\ **Post date:** [August 2, 2017, 9:16pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/11 "2017-08-02T21:16:32Z")
@aliyesami You can leave `transport.host` and `http.host` off entirely. They'll default to the `network.host` property value. The errors you are seeing in your logs indicate that you are failing on the bootstrap checks that run during the Elasticsearch node startup. You can look [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html) for a breakdown for why these checks exist, as well as [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/max-number-threads-check.html) for your specific issue in the logs. ---
**Author:** ![aliyesami](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@aliyesami](https://discuss.elastic.co/u/aliyesami)\ **Post date:** [August 2, 2017, 11:46pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/12 "2017-08-02T23:46:29Z")
awesome thanks ! after I removed the two parameters you mentioned and added the nproc and nofiles parameter to /etc/security/limits.conf the cluster came up . It also fixed my other issue of hive not being able to read the created index. appreciate your help ---
**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\ **Post date:** [August 3, 2017, 3:52pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/13 "2017-08-03T15:52:20Z")
Glad to hear! Cheers 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 31, 2017, 3:52pm UTC](https://discuss.elastic.co/t/missing-index-issue-in-a-cluster/95210/14 "2017-08-31T15:52:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.