# Simple question about a two-node cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [February 4, 2014, 11:50pm UTC](https://discuss.elastic.co/t/simple-question-about-a-two-node-cluster/15605 "2014-02-04T23:50:27Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![jackpark](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jackpark](https://discuss.elastic.co/u/jackpark)\ **Post date:** [February 4, 2014, 11:50pm UTC](https://discuss.elastic.co/t/simple-question-about-a-two-node-cluster/15605/1 "2014-02-04T23:50:27Z")
I confess that, at least for me, documentation, including purchased books, remains a bit ambiguous, where the context is that of making my ES client talk to two different servers. In the end, I did nothing to the elasticsearch.yml files at each server; it simply was not clear what needed to be changed. I did present two IP addresses to the client, but nothing else. That is, I didn't set "sniff" to true, or tell it to ignore cluster names since each server box has just one ES installation running. At startup, I could see that both servers were responding, but soon they each blew up with a flurry of error messages which mean little to me. I bet they're meaningful, except that somewhere near the top where the initial error occurred and which is no-longer visible, perhaps something important was stated. The client's log file correctly stated: connected to 10.1.10.179:9300 and connected to 10.1.10.178:9300 but the log of the 179 server said words to this effect: zen-disco-node\_failed[...][inet 10.1.10.80:9301] I guess I missed something: I don't have a 10.1.10.80 on that network... On the surface, is there something obvious I missed? Many thanks in advance for ideas. Jack -- 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/CAH6s0fyQeqoOo0C\_2VRp1dtK7sOW4DUWv3yByqccGo78DNAbdg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fyQeqoOo0C_2VRp1dtK7sOW4DUWv3yByqccGo78DNAbdg%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Tony\_Su](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@Tony\_Su](https://discuss.elastic.co/u/Tony_Su)\ **Post date:** [February 5, 2014, 12:06am UTC](https://discuss.elastic.co/t/simple-question-about-a-two-node-cluster/15605/2 "2014-02-05T00:06:14Z")
Hi Jack, Although I'm a bit new to this, too... 1. You should take a look at your ES log files. Depending on how you installed and are running ES, the log files could be in different places. If I were to guess though, you should look in the following directory /var/log/elasticsearch/ 2. One of the first things I did was to install and run elasticsearch-head to get near-runtime visibility the status and distribution of the nodes, indexes, shards, etc. HTH, Tony On Tuesday, February 4, 2014 3:50:27 PM UTC-8, Jack Park wrote: > I confess that, at least for me, documentation, including purchased > books, remains a bit ambiguous, where the context is that of making my > ES client talk to two different servers. > > In the end, I did nothing to the elasticsearch.yml files at each > server; it simply was not clear what needed to be changed. > > I did present two IP addresses to the client, but nothing else. That > is, I didn't set "sniff" to true, or tell it to ignore cluster names > since each server box has just one ES installation running. > > At startup, I could see that both servers were responding, but soon > they each blew up with a flurry of error messages which mean little to > me. I bet they're meaningful, except that somewhere near the top where > the initial error occurred and which is no-longer visible, perhaps > something important was stated. > > The client's log file correctly stated: > connected to 10.1.10.179:9300 > and > connected to 10.1.10.178:9300 > > but the log of the 179 server said words to this effect: > zen-disco-node\_failed[...][inet 10.1.10.80:9301] > > I guess I missed something: I don't have a 10.1.10.80 on that network... > > On the surface, is there something obvious I missed? > > Many thanks in advance for ideas. > > Jack -- 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/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jackpark](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jackpark](https://discuss.elastic.co/u/jackpark)\ **Post date:** [February 5, 2014, 1:09am UTC](https://discuss.elastic.co/t/simple-question-about-a-two-node-cluster/15605/3 "2014-02-05T01:09:52Z")
Hi Tony, I did look at the logs. Also, I restarted everything and followed the instructions found at > **[ElasticSearch cluster setup in 2 minutes - Technology Blog](http://techhari.blogspot.com/2013/03/elasticsearch-cluster-setup-in-2-minutes.html)** > > YOUR DISCRIPTION Both nodes are started; I got a message from the first one that it added a cluster when the second node started. I then opened a browser and got the JSON string indicated on that page, meaning, at least to me, that I have an operating cluster. Next up is to fire up the client again and see if things explode again. In the last run, I was sending over data to be indexed, and the client's log never showed any signs of distress, even thought the consoles of both servers were filling with error messages. Jack On Tue, Feb 4, 2014 at 4:06 PM, Tony Su [tonysu999@gmail.com](mailto:tonysu999@gmail.com) wrote: > Hi Jack, > Although I'm a bit new to this, too... > > 1. You should take a look at your ES log files. Depending on how you > installed and are running ES, the log files could be in different places. If > I were to guess though, you should look in the following directory > /var/log/elasticsearch/ > > 2. One of the first things I did was to install and run elasticsearch-head > to get near-runtime visibility the status and distribution of the nodes, > indexes, shards, etc. > > HTH, > Tony > > On Tuesday, February 4, 2014 3:50:27 PM UTC-8, Jack Park wrote: > > > I confess that, at least for me, documentation, including purchased > > books, remains a bit ambiguous, where the context is that of making my > > ES client talk to two different servers. > > > > In the end, I did nothing to the elasticsearch.yml files at each > > server; it simply was not clear what needed to be changed. > > > > I did present two IP addresses to the client, but nothing else. That > > is, I didn't set "sniff" to true, or tell it to ignore cluster names > > since each server box has just one ES installation running. > > > > At startup, I could see that both servers were responding, but soon > > they each blew up with a flurry of error messages which mean little to > > me. I bet they're meaningful, except that somewhere near the top where > > the initial error occurred and which is no-longer visible, perhaps > > something important was stated. > > > > The client's log file correctly stated: > > connected to 10.1.10.179:9300 > > and > > connected to 10.1.10.178:9300 > > > > but the log of the 179 server said words to this effect: > > zen-disco-node\_failed[...][inet 10.1.10.80:9301] > > > > I guess I missed something: I don't have a 10.1.10.80 on that network... > > > > On the surface, is there something obvious I missed? > > > > Many thanks in advance for ideas. > > > > Jack > > -- > 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/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES\_fA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES_fA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [February 5, 2014, 1:13am UTC](https://discuss.elastic.co/t/simple-question-about-a-two-node-cluster/15605/4 "2014-02-05T01:13:48Z")
What client are you using? You'd be well placed to install a plugin such as elastichq or kopf to monitor things as well. It might help tell you where this other node (10.1.10.80) is coming from. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 5 February 2014 12:09, Jack Park [jackpark@topicquests.org](mailto:jackpark@topicquests.org) wrote: > Hi Tony, > > I did look at the logs. > > Also, I restarted everything and followed the instructions found at > > [ElasticSearch cluster setup in 2 minutes - Technology Blog](http://techhari.blogspot.com/2013/03/elasticsearch-cluster-setup-in-2-minutes.html) > > Both nodes are started; I got a message from the first one that it > added a cluster when the second node started. > I then opened a browser and got the JSON string indicated on that > page, meaning, at least to me, that I have an operating cluster. > > Next up is to fire up the client again and see if things explode > again. In the last run, I was sending over data to be indexed, and the > client's log never showed any signs of distress, even thought the > consoles of both servers were filling with error messages. > > Jack > > On Tue, Feb 4, 2014 at 4:06 PM, Tony Su [tonysu999@gmail.com](mailto:tonysu999@gmail.com) wrote: > > > Hi Jack, > > Although I'm a bit new to this, too... > > > > 1. You should take a look at your ES log files. Depending on how you > > installed and are running ES, the log files could be in different > > places. If > > I were to guess though, you should look in the following directory > > /var/log/elasticsearch/ > > > > 2. One of the first things I did was to install and run > > elasticsearch-head > > to get near-runtime visibility the status and distribution of the nodes, > > indexes, shards, etc. > > > > HTH, > > Tony > > > > On Tuesday, February 4, 2014 3:50:27 PM UTC-8, Jack Park wrote: > > > > > I confess that, at least for me, documentation, including purchased > > > books, remains a bit ambiguous, where the context is that of making my > > > ES client talk to two different servers. > > > > > > In the end, I did nothing to the elasticsearch.yml files at each > > > server; it simply was not clear what needed to be changed. > > > > > > I did present two IP addresses to the client, but nothing else. That > > > is, I didn't set "sniff" to true, or tell it to ignore cluster names > > > since each server box has just one ES installation running. > > > > > > At startup, I could see that both servers were responding, but soon > > > they each blew up with a flurry of error messages which mean little to > > > me. I bet they're meaningful, except that somewhere near the top where > > > the initial error occurred and which is no-longer visible, perhaps > > > something important was stated. > > > > > > The client's log file correctly stated: > > > connected to 10.1.10.179:9300 > > > and > > > connected to 10.1.10.178:9300 > > > > > > but the log of the 179 server said words to this effect: > > > zen-disco-node\_failed[...][inet 10.1.10.80:9301] > > > > > > I guess I missed something: I don't have a 10.1.10.80 on that network... > > > > > > On the surface, is there something obvious I missed? > > > > > > Many thanks in advance for ideas. > > > > > > Jack > > > > -- > > 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/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES\_fA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES_fA%40mail.gmail.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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624bvPe\_Ukq73aejBJkxNugSmjeHeF0RE7D-m0Vf0rb%3DX%3DQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bvPe_Ukq73aejBJkxNugSmjeHeF0RE7D-m0Vf0rb%3DX%3DQ%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jackpark](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jackpark](https://discuss.elastic.co/u/jackpark)\ **Post date:** [February 5, 2014, 1:20am UTC](https://discuss.elastic.co/t/simple-question-about-a-two-node-cluster/15605/5 "2014-02-05T01:20:50Z")
That's very timely. The second-to-start node is receiving a join request from 10.1.10.80:9303 even though 10.1.10.80 does not ping from anywhere in the network I'll look into adding [http://www.elastichq.org/](http://www.elastichq.org/) to the browser and see what it says. Many thanks Jack On Tue, Feb 4, 2014 at 5:13 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > What client are you using? > > You'd be well placed to install a plugin such as elastichq or kopf to > monitor things as well. It might help tell you where this other node > (10.1.10.80) is coming from. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 5 February 2014 12:09, Jack Park [jackpark@topicquests.org](mailto:jackpark@topicquests.org) wrote: > > > Hi Tony, > > > > I did look at the logs. > > > > Also, I restarted everything and followed the instructions found at > > > > [ElasticSearch cluster setup in 2 minutes - Technology Blog](http://techhari.blogspot.com/2013/03/elasticsearch-cluster-setup-in-2-minutes.html) > > > > Both nodes are started; I got a message from the first one that it > > added a cluster when the second node started. > > I then opened a browser and got the JSON string indicated on that > > page, meaning, at least to me, that I have an operating cluster. > > > > Next up is to fire up the client again and see if things explode > > again. In the last run, I was sending over data to be indexed, and the > > client's log never showed any signs of distress, even thought the > > consoles of both servers were filling with error messages. > > > > Jack > > > > On Tue, Feb 4, 2014 at 4:06 PM, Tony Su [tonysu999@gmail.com](mailto:tonysu999@gmail.com) wrote: > > > > > Hi Jack, > > > Although I'm a bit new to this, too... > > > > > > 1. You should take a look at your ES log files. Depending on how you > > > installed and are running ES, the log files could be in different > > > places. If > > > I were to guess though, you should look in the following directory > > > /var/log/elasticsearch/ > > > > > > 2. One of the first things I did was to install and run > > > elasticsearch-head > > > to get near-runtime visibility the status and distribution of the nodes, > > > indexes, shards, etc. > > > > > > HTH, > > > Tony > > > > > > On Tuesday, February 4, 2014 3:50:27 PM UTC-8, Jack Park wrote: > > > > > > > I confess that, at least for me, documentation, including purchased > > > > books, remains a bit ambiguous, where the context is that of making my > > > > ES client talk to two different servers. > > > > > > > > In the end, I did nothing to the elasticsearch.yml files at each > > > > server; it simply was not clear what needed to be changed. > > > > > > > > I did present two IP addresses to the client, but nothing else. That > > > > is, I didn't set "sniff" to true, or tell it to ignore cluster names > > > > since each server box has just one ES installation running. > > > > > > > > At startup, I could see that both servers were responding, but soon > > > > they each blew up with a flurry of error messages which mean little to > > > > me. I bet they're meaningful, except that somewhere near the top where > > > > the initial error occurred and which is no-longer visible, perhaps > > > > something important was stated. > > > > > > > > The client's log file correctly stated: > > > > connected to 10.1.10.179:9300 > > > > and > > > > connected to 10.1.10.178:9300 > > > > > > > > but the log of the 179 server said words to this effect: > > > > zen-disco-node\_failed[...][inet 10.1.10.80:9301] > > > > > > > > I guess I missed something: I don't have a 10.1.10.80 on that > > > > network... > > > > > > > > On the surface, is there something obvious I missed? > > > > > > > > Many thanks in advance for ideas. > > > > > > > > Jack > > > > > > -- > > > 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/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.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). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES\_fA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES_fA%40mail.gmail.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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEM624bvPe\_Ukq73aejBJkxNugSmjeHeF0RE7D-m0Vf0rb%3DX%3DQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bvPe_Ukq73aejBJkxNugSmjeHeF0RE7D-m0Vf0rb%3DX%3DQ%40mail.gmail.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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAH6s0fwd9nRi5sK1tTjT8ObLvH0fVfs9Cu7E7ycNuudRDxaLRg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fwd9nRi5sK1tTjT8ObLvH0fVfs9Cu7E7ycNuudRDxaLRg%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [February 5, 2014, 1:23am UTC](https://discuss.elastic.co/t/simple-question-about-a-two-node-cluster/15605/6 "2014-02-05T01:23:26Z")
Did you change the cluster name as the blog suggested? And can you clarify what client you are using as well? Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 5 February 2014 12:20, Jack Park [jackpark@topicquests.org](mailto:jackpark@topicquests.org) wrote: > That's very timely. > > The second-to-start node is receiving a join request from 10.1.10.80:9303 > even though 10.1.10.80 does not ping from anywhere in the network > > I'll look into adding [http://www.elastichq.org/](http://www.elastichq.org/) to the browser and see > what it says. > > Many thanks > Jack > > On Tue, Feb 4, 2014 at 5:13 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > wrote: > > > What client are you using? > > > > You'd be well placed to install a plugin such as elastichq or kopf to > > monitor things as well. It might help tell you where this other node > > (10.1.10.80) is coming from. > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > On 5 February 2014 12:09, Jack Park [jackpark@topicquests.org](mailto:jackpark@topicquests.org) wrote: > > > > > Hi Tony, > > > > > > I did look at the logs. > > > > > > Also, I restarted everything and followed the instructions found at > > [ElasticSearch cluster setup in 2 minutes - Technology Blog](http://techhari.blogspot.com/2013/03/elasticsearch-cluster-setup-in-2-minutes.html) > > > > Both nodes are started; I got a message from the first one that it > > > added a cluster when the second node started. > > > I then opened a browser and got the JSON string indicated on that > > > page, meaning, at least to me, that I have an operating cluster. > > > > > > Next up is to fire up the client again and see if things explode > > > again. In the last run, I was sending over data to be indexed, and the > > > client's log never showed any signs of distress, even thought the > > > consoles of both servers were filling with error messages. > > > > > > Jack > > > > > > On Tue, Feb 4, 2014 at 4:06 PM, Tony Su [tonysu999@gmail.com](mailto:tonysu999@gmail.com) wrote: > > > > > > > Hi Jack, > > > > Although I'm a bit new to this, too... > > > > > > > > 1. You should take a look at your ES log files. Depending on how you > > > > installed and are running ES, the log files could be in different > > > > places. If > > > > I were to guess though, you should look in the following directory > > > > /var/log/elasticsearch/ > > > > > > > > 2. One of the first things I did was to install and run > > > > elasticsearch-head > > > > to get near-runtime visibility the status and distribution of the > > > > nodes, > > > > indexes, shards, etc. > > > > > > > > HTH, > > > > Tony > > > > > > > > On Tuesday, February 4, 2014 3:50:27 PM UTC-8, Jack Park wrote: > > > > > > > > > I confess that, at least for me, documentation, including purchased > > > > > books, remains a bit ambiguous, where the context is that of making > > > > > my > > > > > ES client talk to two different servers. > > > > > > > > > > In the end, I did nothing to the elasticsearch.yml files at each > > > > > server; it simply was not clear what needed to be changed. > > > > > > > > > > I did present two IP addresses to the client, but nothing else. That > > > > > is, I didn't set "sniff" to true, or tell it to ignore cluster names > > > > > since each server box has just one ES installation running. > > > > > > > > > > At startup, I could see that both servers were responding, but soon > > > > > they each blew up with a flurry of error messages which mean little > > > > > to > > > > > me. I bet they're meaningful, except that somewhere near the top > > > > > where > > > > > the initial error occurred and which is no-longer visible, perhaps > > > > > something important was stated. > > > > > > > > > > The client's log file correctly stated: > > > > > connected to 10.1.10.179:9300 > > > > > and > > > > > connected to 10.1.10.178:9300 > > > > > > > > > > but the log of the 179 server said words to this effect: > > > > > zen-disco-node\_failed[...][inet 10.1.10.80:9301] > > > > > > > > > > I guess I missed something: I don't have a 10.1.10.80 on that > > > > > network... > > > > > > > > > > On the surface, is there something obvious I missed? > > > > > > > > > > Many thanks in advance for ideas. > > > > > > > > > > Jack > > > > > > > > -- > > > > 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/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.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). > > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES\_fA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES_fA%40mail.gmail.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). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAEM624bvPe\_Ukq73aejBJkxNugSmjeHeF0RE7D-m0Vf0rb%3DX%3DQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bvPe_Ukq73aejBJkxNugSmjeHeF0RE7D-m0Vf0rb%3DX%3DQ%40mail.gmail.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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAH6s0fwd9nRi5sK1tTjT8ObLvH0fVfs9Cu7E7ycNuudRDxaLRg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fwd9nRi5sK1tTjT8ObLvH0fVfs9Cu7E7ycNuudRDxaLRg%40mail.gmail.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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624YCrh0%2ByP%2BCZxDp4admq5vfbZyvdzJOMZPLBq\_Utvzw5Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YCrh0%2ByP%2BCZxDp4admq5vfbZyvdzJOMZPLBq_Utvzw5Q%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jackpark](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jackpark](https://discuss.elastic.co/u/jackpark)\ **Post date:** [February 5, 2014, 1:51am UTC](https://discuss.elastic.co/t/simple-question-about-a-two-node-cluster/15605/7 "2014-02-05T01:51:18Z")
I left everything as defaults. The client is based on ES 0.90.7 using TransportClient. I just restarted the entire platform, got a clean set of logs after startup. Then, started my program. While it was booting, both servers went wild with error messages on the console, then settled down. So, I started the import process. The game is to build a topic map and several word graphs while importing ontologies. Right now, it gives every indication that it's running; lights indicating disk activity on both servers are active, and the consoles reflect no distress. Didn't look at logs. Still no clues, but running, at least for the moment. Running the same platform on a single server went without any errors. The full import took 5 days. I'd like to hope this will run faster. Thanks Jack On Tue, Feb 4, 2014 at 5:23 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > Did you change the cluster name as the blog suggested? > > And can you clarify what client you are using as well? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 5 February 2014 12:20, Jack Park [jackpark@topicquests.org](mailto:jackpark@topicquests.org) wrote: > > > That's very timely. > > > > The second-to-start node is receiving a join request from 10.1.10.80:9303 > > even though 10.1.10.80 does not ping from anywhere in the network > > > > I'll look into adding [http://www.elastichq.org/](http://www.elastichq.org/) to the browser and see > > what it says. > > > > Many thanks > > Jack > > > > On Tue, Feb 4, 2014 at 5:13 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > wrote: > > > > > What client are you using? > > > > > > You'd be well placed to install a plugin such as elastichq or kopf to > > > monitor things as well. It might help tell you where this other node > > > (10.1.10.80) is coming from. > > > > > > Regards, > > > Mark Walkom > > > > > > Infrastructure Engineer > > > Campaign Monitor > > > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > > > On 5 February 2014 12:09, Jack Park [jackpark@topicquests.org](mailto:jackpark@topicquests.org) wrote: > > > > > > > Hi Tony, > > > > > > > > I did look at the logs. > > > > > > > > Also, I restarted everything and followed the instructions found at > > > > > > > > [ElasticSearch cluster setup in 2 minutes - Technology Blog](http://techhari.blogspot.com/2013/03/elasticsearch-cluster-setup-in-2-minutes.html) > > > > > > > > Both nodes are started; I got a message from the first one that it > > > > added a cluster when the second node started. > > > > I then opened a browser and got the JSON string indicated on that > > > > page, meaning, at least to me, that I have an operating cluster. > > > > > > > > Next up is to fire up the client again and see if things explode > > > > again. In the last run, I was sending over data to be indexed, and the > > > > client's log never showed any signs of distress, even thought the > > > > consoles of both servers were filling with error messages. > > > > > > > > Jack > > > > > > > > On Tue, Feb 4, 2014 at 4:06 PM, Tony Su [tonysu999@gmail.com](mailto:tonysu999@gmail.com) wrote: > > > > > > > > > Hi Jack, > > > > > Although I'm a bit new to this, too... > > > > > > > > > > 1. You should take a look at your ES log files. Depending on how you > > > > > installed and are running ES, the log files could be in different > > > > > places. If > > > > > I were to guess though, you should look in the following directory > > > > > /var/log/elasticsearch/ > > > > > > > > > > 2. One of the first things I did was to install and run > > > > > elasticsearch-head > > > > > to get near-runtime visibility the status and distribution of the > > > > > nodes, > > > > > indexes, shards, etc. > > > > > > > > > > HTH, > > > > > Tony > > > > > > > > > > On Tuesday, February 4, 2014 3:50:27 PM UTC-8, Jack Park wrote: > > > > > > > > > > > I confess that, at least for me, documentation, including purchased > > > > > > books, remains a bit ambiguous, where the context is that of making > > > > > > my > > > > > > ES client talk to two different servers. > > > > > > > > > > > > In the end, I did nothing to the elasticsearch.yml files at each > > > > > > server; it simply was not clear what needed to be changed. > > > > > > > > > > > > I did present two IP addresses to the client, but nothing else. That > > > > > > is, I didn't set "sniff" to true, or tell it to ignore cluster names > > > > > > since each server box has just one ES installation running. > > > > > > > > > > > > At startup, I could see that both servers were responding, but soon > > > > > > they each blew up with a flurry of error messages which mean little > > > > > > to > > > > > > me. I bet they're meaningful, except that somewhere near the top > > > > > > where > > > > > > the initial error occurred and which is no-longer visible, perhaps > > > > > > something important was stated. > > > > > > > > > > > > The client's log file correctly stated: > > > > > > connected to 10.1.10.179:9300 > > > > > > and > > > > > > connected to 10.1.10.178:9300 > > > > > > > > > > > > but the log of the 179 server said words to this effect: > > > > > > zen-disco-node\_failed[...][inet 10.1.10.80:9301] > > > > > > > > > > > > I guess I missed something: I don't have a 10.1.10.80 on that > > > > > > network... > > > > > > > > > > > > On the surface, is there something obvious I missed? > > > > > > > > > > > > Many thanks in advance for ideas. > > > > > > > > > > > > Jack > > > > > > > > > > -- > > > > > 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/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d4c504d2-402f-4028-9ce4-ffe87e43dd28%40googlegroups.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). > > > > To view this discussion on the web visit > > > > > > > > [https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES\_fA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw29a5hwrHv%3D2e0gtSW5FJaunqG5E2Znzg%3DE1PUvES_fA%40mail.gmail.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). > > > To view this discussion on the web visit > > > > > > [https://groups.google.com/d/msgid/elasticsearch/CAEM624bvPe\_Ukq73aejBJkxNugSmjeHeF0RE7D-m0Vf0rb%3DX%3DQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bvPe_Ukq73aejBJkxNugSmjeHeF0RE7D-m0Vf0rb%3DX%3DQ%40mail.gmail.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). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAH6s0fwd9nRi5sK1tTjT8ObLvH0fVfs9Cu7E7ycNuudRDxaLRg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fwd9nRi5sK1tTjT8ObLvH0fVfs9Cu7E7ycNuudRDxaLRg%40mail.gmail.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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEM624YCrh0%2ByP%2BCZxDp4admq5vfbZyvdzJOMZPLBq\_Utvzw5Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YCrh0%2ByP%2BCZxDp4admq5vfbZyvdzJOMZPLBq_Utvzw5Q%40mail.gmail.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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAH6s0fzZS0hw5qkiaZ7RuLE8XfaazU6SgaRU8QWZiJj4ges4bw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAH6s0fzZS0hw5qkiaZ7RuLE8XfaazU6SgaRU8QWZiJj4ges4bw%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:52am UTC](https://discuss.elastic.co/t/simple-question-about-a-two-node-cluster/15605/8 "2017-07-06T01:52:35Z")