# Cluster management **URL:** \ **Category:** Elasticsearch\ **Created:** [May 14, 2013, 11:35am UTC](https://discuss.elastic.co/t/cluster-management/11952 "2013-05-14T11:35:04Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Chethan\_Prasad](https://avatars.discourse-cdn.com/v4/letter/c/d78d45/32.png) [@Chethan\_Prasad](https://discuss.elastic.co/u/Chethan_Prasad)\ **Post date:** [May 14, 2013, 11:35am UTC](https://discuss.elastic.co/t/cluster-management/11952/1 "2013-05-14T11:35:04Z")
Hi, new to ElasticSearch and this may be a noob question. When a node in a cluster goes down, how does the client realize that it's not supposed to hit that IP or more importantly that port in case of more than one nodes on a server? Seems to me like the clients need to maintain metadata about the cluster and loop through that if the request fails. Thanks Chethan -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![radu\_gheorghe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/radu_gheorghe/32/556_2.png) [@radu\_gheorghe](https://discuss.elastic.co/u/radu_gheorghe)\ **Post date:** [May 14, 2013, 12:08pm UTC](https://discuss.elastic.co/t/cluster-management/11952/2 "2013-05-14T12:08:50Z")
Hello Chethan, Yes, I think you'll need to loop from your application, or use a load balancer. Although, if the load balancer goes down, you're back to square 1. Some clients (pyes, for example) accept an array of addresses, and handle that for you. ## Best regards, Radu [http://sematext.com/](http://sematext.com/) -- Elasticsearch -- Solr -- Lucene On Tue, May 14, 2013 at 2:35 PM, Chethan Prasad [chethan.p.04@gmail.com](mailto:chethan.p.04@gmail.com)wrote: > Hi, new to Elasticsearch and this may be a noob question. When a node in a > cluster goes down, how does the client realize that it's not supposed to > hit that IP or more importantly that port in case of more than one nodes on > a server? Seems to me like the clients need to maintain metadata about the > cluster and loop through that if the request fails. > > Thanks > Chethan > > -- > 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). > 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Chethan\_Prasad](https://avatars.discourse-cdn.com/v4/letter/c/d78d45/32.png) [@Chethan\_Prasad](https://discuss.elastic.co/u/Chethan_Prasad)\ **Post date:** [May 14, 2013, 12:24pm UTC](https://discuss.elastic.co/t/cluster-management/11952/3 "2013-05-14T12:24:14Z")
Hello Radu, Thanks for the response. Although I understand adding something like a name node is not all that wise because then it brings in a single point of failure. But I think techniques used by Cassandra can be adopted here. It may be a good idea for a fork. Thanks Chethan On Tue, May 14, 2013 at 5:38 PM, Radu Gheorghe [radu.gheorghe@sematext.com](mailto:radu.gheorghe@sematext.com)wrote: > Hello Chethan, > > Yes, I think you'll need to loop from your application, or use a load > balancer. Although, if the load balancer goes down, you're back to square 1. > > Some clients (pyes, for example) accept an array of addresses, and handle > that for you. > > ## Best regards, Radu > > [http://sematext.com/](http://sematext.com/) -- Elasticsearch -- Solr -- Lucene > > On Tue, May 14, 2013 at 2:35 PM, Chethan Prasad [chethan.p.04@gmail.com](mailto:chethan.p.04@gmail.com)wrote: > > > Hi, new to Elasticsearch and this may be a noob question. When a node in > > a cluster goes down, how does the client realize that it's not supposed to > > hit that IP or more importantly that port in case of more than one nodes on > > a server? Seems to me like the clients need to maintain metadata about the > > cluster and loop through that if the request fails. > > > > Thanks > > Chethan > > > > -- > > 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). > > > > 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 a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/ZKg3fbm\_Z2Q/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/ZKg3fbm_Z2Q/unsubscribe?hl=en-US) > . > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [May 15, 2013, 9:23am UTC](https://discuss.elastic.co/t/cluster-management/11952/4 "2013-05-15T09:23:03Z")
Hi Chethan What client are you talking about? The elasticsearch Java node client? The transport client? One of the REST clients? The Java clients can sniff a list of live nodes and so will remove dead nodes. (client.transport.sniff: true) Some of the REST clients do this as well and there are plans afoot to support this in all REST clients clint On Tue, May 14, 2013 at 2:24 PM, chethan [chethan.p.04@gmail.com](mailto:chethan.p.04@gmail.com) wrote: > Hello Radu, > > Thanks for the response. Although I understand adding something like a > name node is not all that wise because then it brings in a single point of > failure. But I think techniques used by Cassandra can be adopted here. It > may be a good idea for a fork. > > Thanks > Chethan > > On Tue, May 14, 2013 at 5:38 PM, Radu Gheorghe \<[radu.gheorghe@sematext.com](mailto:radu.gheorghe@sematext.com) > > > wrote: > > > Hello Chethan, > > > > Yes, I think you'll need to loop from your application, or use a load > > balancer. Although, if the load balancer goes down, you're back to square 1. > > > > Some clients (pyes, for example) accept an array of addresses, and handle > > that for you. > > > > ## Best regards, Radu > > > > [http://sematext.com/](http://sematext.com/) -- Elasticsearch -- Solr -- Lucene > > > > On Tue, May 14, 2013 at 2:35 PM, Chethan Prasad [chethan.p.04@gmail.com](mailto:chethan.p.04@gmail.com)wrote: > > > > > Hi, new to Elasticsearch and this may be a noob question. When a node in > > > a cluster goes down, how does the client realize that it's not supposed to > > > hit that IP or more importantly that port in case of more than one nodes on > > > a server? Seems to me like the clients need to maintain metadata about the > > > cluster and loop through that if the request fails. > > > > > > Thanks > > > Chethan > > > > > > -- > > > 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). > > > > > > 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 a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/ZKg3fbm\_Z2Q/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/ZKg3fbm_Z2Q/unsubscribe?hl=en-US) > > . > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > 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). > 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Chethan\_Prasad](https://avatars.discourse-cdn.com/v4/letter/c/d78d45/32.png) [@Chethan\_Prasad](https://discuss.elastic.co/u/Chethan_Prasad)\ **Post date:** [May 15, 2013, 9:30am UTC](https://discuss.elastic.co/t/cluster-management/11952/5 "2013-05-15T09:30:20Z")
Hi, I was talking about just using REST. Thanks Chethan On Wed, May 15, 2013 at 2:53 PM, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)wrote: > Hi Chethan > > What client are you talking about? The elasticsearch Java node client? The > transport client? One of the REST clients? > > The Java clients can sniff a list of live nodes and so will remove dead > nodes. (client.transport.sniff: true) > > Some of the REST clients do this as well and there are plans afoot to > support this in all REST clients > > clint > > On Tue, May 14, 2013 at 2:24 PM, chethan [chethan.p.04@gmail.com](mailto:chethan.p.04@gmail.com) wrote: > > > Hello Radu, > > > > Thanks for the response. Although I understand adding something like a > > name node is not all that wise because then it brings in a single point of > > failure. But I think techniques used by Cassandra can be adopted here. It > > may be a good idea for a fork. > > > > Thanks > > Chethan > > > > On Tue, May 14, 2013 at 5:38 PM, Radu Gheorghe \< > > [radu.gheorghe@sematext.com](mailto:radu.gheorghe@sematext.com)\> wrote: > > > > > Hello Chethan, > > > > > > Yes, I think you'll need to loop from your application, or use a load > > > balancer. Although, if the load balancer goes down, you're back to square 1. > > > > > > Some clients (pyes, for example) accept an array of addresses, and > > > handle that for you. > > > > > > ## Best regards, Radu > > > > > > [http://sematext.com/](http://sematext.com/) -- Elasticsearch -- Solr -- Lucene > > > > > > On Tue, May 14, 2013 at 2:35 PM, Chethan Prasad [chethan.p.04@gmail.com](mailto:chethan.p.04@gmail.com)wrote: > > > > > > > Hi, new to Elasticsearch and this may be a noob question. When a node > > > > in a cluster goes down, how does the client realize that it's not supposed > > > > to hit that IP or more importantly that port in case of more than one nodes > > > > on a server? Seems to me like the clients need to maintain metadata about > > > > the cluster and loop through that if the request fails. > > > > > > > > Thanks > > > > Chethan > > > > > > > > -- > > > > 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). > > > > > > > > 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 a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/ZKg3fbm\_Z2Q/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/ZKg3fbm_Z2Q/unsubscribe?hl=en-US) > > > . > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > > > 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). > > 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 a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/ZKg3fbm\_Z2Q/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/ZKg3fbm_Z2Q/unsubscribe?hl=en-US) > . > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [May 15, 2013, 9:34am UTC](https://discuss.elastic.co/t/cluster-management/11952/6 "2013-05-15T09:34:55Z")
I add to Clint's answer the following link that should help you as well: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/java-api/client/) -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 15 mai 2013 à 11:23, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com) a écrit : > Hi Chethan > > What client are you talking about? The elasticsearch Java node client? The transport client? One of the REST clients? > > The Java clients can sniff a list of live nodes and so will remove dead nodes. (client.transport.sniff: true) > > Some of the REST clients do this as well and there are plans afoot to support this in all REST clients > > clint > > On Tue, May 14, 2013 at 2:24 PM, chethan [chethan.p.04@gmail.com](mailto:chethan.p.04@gmail.com) wrote: > Hello Radu, > > Thanks for the response. Although I understand adding something like a name node is not all that wise because then it brings in a single point of failure. But I think techniques used by Cassandra can be adopted here. It may be a good idea for a fork. > > Thanks > Chethan > > On Tue, May 14, 2013 at 5:38 PM, Radu Gheorghe [radu.gheorghe@sematext.com](mailto:radu.gheorghe@sematext.com) wrote: > Hello Chethan, > > Yes, I think you'll need to loop from your application, or use a load balancer. Although, if the load balancer goes down, you're back to square 1. > > Some clients (pyes, for example) accept an array of addresses, and handle that for you. > > ## Best regards, Radu > > [http://sematext.com/](http://sematext.com/) -- Elasticsearch -- Solr -- Lucene > > On Tue, May 14, 2013 at 2:35 PM, Chethan Prasad [chethan.p.04@gmail.com](mailto:chethan.p.04@gmail.com) wrote: > Hi, new to Elasticsearch and this may be a noob question. When a node in a cluster goes down, how does the client realize that it's not supposed to hit that IP or more importantly that port in case of more than one nodes on a server? Seems to me like the clients need to maintain metadata about the cluster and loop through that if the request fails. > > Thanks > Chethan > > -- > 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). > > 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 a topic in the Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit [https://groups.google.com/d/topic/elasticsearch/ZKg3fbm\_Z2Q/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/ZKg3fbm_Z2Q/unsubscribe?hl=en-US). > To unsubscribe from this group and all its topics, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > 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). > 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). > 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, 2:36am UTC](https://discuss.elastic.co/t/cluster-management/11952/7 "2017-07-06T02:36:38Z")