If you just downloaded and started ES then your settings will be default ones.
Change cluster.name to something that isn't elasticsearch, and make sure it is the same on both nodes. Just list both hosts under discovery.zen.ping.unicast.hosts. Also make sure you disable multicast at the same time. Plugins need to be installed on all nodes if you want to access them via any node, however some plugins need to be installed on all hosts regardless, so check the docs. On 27 January 2015 at 08:22, GWired <garrettcjohn...@gmail.com> wrote: > Ok so I looked at the config file and found this: > > cluster.name - which you are saying I set it to the same on both > machines... got it. > > discovery.zen.ping.unicast.hosts: ["host1", "host2:port"] --- since I > am not on the same network in this case they are in different but > accessible domains (crossing DIT and SIT areas... don't get me started). > do I put in the URL of the other engine into this in the elasticsearch for > each one and point it to each other? Like so > > First ES node > discovery.zen.ping.unicast.hosts: ["node2.dit.domain.com:9200"] > > Second ES node > discovery.zen.ping.unicast.hosts: ["node1.sit.domain.com:9200"] > > --------- > This leads me to other questions: > > Do I have to install plugins on each node individually? > > I'm assuming the data figures out how to get to the nodes on it's own. > > I've seen properties in the ElasticSearch.net code that would allow me to > do some kind of discovery for nodes as well in the event one is down. > > > > > > > > > On Monday, January 26, 2015 at 3:34:04 PM UTC-5, GWired wrote: > >> I'm doing this in windows. >> >> I'm crossing internal domains for each node so I thought I'd have to tell >> something somewhere that there is another node. >> >> Also I probably want it configured the same way. >> >> Also I don't see where I select a cluster name for the nodes. >> >> With the single node install all I did was... .install and magic >> happened. I like magic. >> >> I would love if it I just told ES this node to install onto the new node >> and it did all of that for me as long as I have drive letter access etc. >> >> Garrett >> >> >> >> On Monday, January 26, 2015 at 3:06:42 PM UTC-5, Jörg Prante wrote: >> >>> Hey, it is as simple as running the first node. Just install ES, select >>> a cluster name for the nodes, start it on the nodes, and let the node >>> discovery join the nodes. I recommend odd numbers and at least 3 nodes to >>> avoid a split brain. >>> >>> Or did I miss something? >>> >>> Jörg >>> >>> On Mon, Jan 26, 2015 at 8:59 PM, GWired <garrett...@gmail.com> wrote: >>> >>>> Is there a place where someone can point me to a simple set of >>>> instructions for adding a node to an Elastic Search cluster? >>>> >>>> I think I understand Sharding and Nodes and that's what the documents >>>> do is talk about them. >>>> >>>> But what I don't understand is... >>>> >>>> How do install ElasticSearch on the second node. >>>> If I'm only able to have a two node cluster that will be both a >>>> failover and maybe some perf boost, how do I ensure that I've set all my >>>> settings correctly. (Looks like my rivers setup 4 shards). Are there any >>>> best practices etc >>>> >>>> I've been googling my fingers off and no luck finding what i'm looking >>>> for. >>>> >>>> If I copy the elastic search folder from one machine to another... how >>>> can i use that to make a replica. >>>> >>>> Garrett >>>> >>>> -- >>>> 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 elasticsearc...@googlegroups.com. >>>> To view this discussion on the web visit https://groups.google.com/d/ >>>> msgid/elasticsearch/2b89ca10-764a-4164-ab02-475b88b1620f% >>>> 40googlegroups.com >>>> <https://groups.google.com/d/msgid/elasticsearch/2b89ca10-764a-4164-ab02-475b88b1620f%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- > 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/30528bf4-f107-4c1d-8307-a0273cee4b93%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/30528bf4-f107-4c1d-8307-a0273cee4b93%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAEYi1X8hES%2BXgpesmpcU9CD6Beu8V%2BWfrHt-_%2BM_vZxxs%3Dfz4Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
