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/ to the browser and see what it says. Many thanks Jack On Tue, Feb 4, 2014 at 5:13 PM, Mark Walkom <ma...@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: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 5 February 2014 12:09, Jack Park <jackp...@topicquests.org> wrote: >> >> Hi Tony, >> >> I did look at the logs. >> >> Also, I restarted everything and followed the instructions found at >> >> 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 <tonysu...@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+unsubscr...@googlegroups.com. >> > To view this discussion on the web visit >> > >> > 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. >> >> -- >> 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+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> 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. > > > -- > 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+unsubscr...@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. > > For more options, visit 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH6s0fwd9nRi5sK1tTjT8ObLvH0fVfs9Cu7E7ycNuudRDxaLRg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
