# ES 6.0 timeout on cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [December 19, 2017, 12:35pm UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434 "2017-12-19T12:35:14Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Rakotobe](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@Rakotobe](https://discuss.elastic.co/u/Rakotobe)\ **Post date:** [December 19, 2017, 12:35pm UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/1 "2017-12-19T12:35:15Z")
Hello, I've 3 differents server with 1 instance of ES 6.0 on each and another server with nodejs, to query on. On each server I just changed : `discovery.zen.ping.unicast.hosts : [LIST_ES_IP]` `discovery.zen.minimum_master_nodes: 2` My problem is that after some times (not define), I've timeout error from nodejs server. But if I call `curl -XGET 'IP:9200/_cluster/health?pretty'` On this same server, I can see that ES works fine. If I remove one server from cluster (comment previous 2 config lines), and query only on it, all works good & I never have timeout. Did I need to change another config to make this cluster works ? Did you have ideas about why I've timeout only on cluster mode ? Thanks in advance, ---
**Author:** ![Rakotobe](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@Rakotobe](https://discuss.elastic.co/u/Rakotobe)\ **Post date:** [December 19, 2017, 6:49pm UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/2 "2017-12-19T18:49:33Z")
Apparently it's cause on **elasticsearch-js** client because I reactivate cluster, but define host to `"IP:9200"` and it works for 3 hours now. Before I've `["IP1:9200", "IP2:9200", "IP3:9200"]` I try with `[{host: "IP", port: 9200}, {...}]` But time out too.. So no way to have rollback if one server failed ? ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [December 20, 2017, 7:17am UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/3 "2017-12-20T07:17:13Z")
> [@Rakotobe](#): > > Before I've > > ["IP1:9200", "IP2:9200", "IP3:9200"] this i think it is **IP:9300** or not use port.. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 20, 2017, 7:31am UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/4 "2017-12-20T07:31:05Z")
It depends. If it's in the context of the JS client, 9200 is ok. If it's `elasticsearch.yml`, then it's indeed 9300. ---
**Author:** ![Rakotobe](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@Rakotobe](https://discuss.elastic.co/u/Rakotobe)\ **Post date:** [December 20, 2017, 11:11am UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/5 "2017-12-20T11:11:25Z")
Yes previous configuration is on JS (node) client via **elasticsearch-js** I've same problem with a python client ( **elasticsearch-py** ). If I try to configurate with multiple host, it throw timeout. On `elasticsearch.yml` I just not write port ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [December 21, 2017, 1:04am UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/6 "2017-12-21T01:04:12Z")
is about this? ``` discovery.zen.publish_timeout: 180s discovery.zen.fd.ping_interval: 60s discovery.zen.fd.ping_timeout: 180s discovery.zen.fd.ping_retries: 10 discovery.zen.commit_timeout: 180s ``` ---
**Author:** ![Rakotobe](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@Rakotobe](https://discuss.elastic.co/u/Rakotobe)\ **Post date:** [December 21, 2017, 2:19am UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/7 "2017-12-21T02:19:48Z")
Hum it's works better from 1hour for now. I'll continue to make some tests comming days. Thanks a lot if it's solved by this config. ---
**Author:** ![Rakotobe](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@Rakotobe](https://discuss.elastic.co/u/Rakotobe)\ **Post date:** [December 21, 2017, 3:17am UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/8 "2017-12-21T03:17:49Z")
Nope already timeout. Really don't know why.. I transfer my old ES2.1 data on my ES6.0 cluster (3 200 000 products), and now I've timeout even if I connect to only one node. ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [December 21, 2017, 3:37am UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/9 "2017-12-21T03:37:20Z")
how many bulk onces? show the cluster status, show the nodes status. show the logs . about master and data nodes. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 18, 2018, 3:37am UTC](https://discuss.elastic.co/t/es-6-0-timeout-on-cluster/112434/10 "2018-01-18T03:37:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.