I've been messing with things on Host2 and it will no longer Start as a
service but when Iaunch it as myself logged in it does this...
[2015-01-29 20:44:54,480][INFO ][transport ] [Cat]
bound_address
{inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.160.129.57:9300]}
[2015-01-29 20:44:54,530][INFO ][discovery ] [Cat]
ESMyName/efU
1z15ERPCS3qOVb5posA
[2015-01-29 20:44:57,590][INFO ][cluster.service ] [Cat]
new_master [Ca
t][efU1z15ERPCS3qOVb5posA][HOST2][inet[/10.160.129.57:9300]], reason:
zen-disco-join (elected_as_master)
[2015-01-29 20:44:57,804][INFO ][http ] [Cat]
bound_address
{inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.160.129.57:9200]}
[2015-01-29 20:44:57,805][INFO ][node ] [Cat] started
On Thursday, January 29, 2015 at 9:07:37 PM UTC-5, GWired wrote:
>
> host1 elasticsearch.yml
> https://gist.github.com/anonymous/1db14fe7fcd93013defc
>
> Host2 elasticsearch.yml:
> https://gist.github.com/anonymous/b4ac49f2a2a559204632
>
>
>
> On Thursday, January 29, 2015 at 4:49:33 PM UTC-5, Mark Walkom wrote:
>>
>> Then your nodes have not joined together.
>>
>> Can you gist/pastebin/etc your configs so we can check them?
>>
>> On 29 January 2015 at 14:56, GWired <[email protected]> wrote:
>>
>>> On my initial host (host1) I changed my cluster.name to
>>>
>>> cluster.name: ESMyName
>>>
>>> Which in elasticsearchhead it is showing as the new name.
>>>
>>> I also uncommented::
>>>
>>> discovery.zen.ping.multicast.enabled: false
>>>
>>> And added
>>>
>>> discovery.zen.ping.unicast.hosts: ["host2.mydomain.com:9200"]
>>>
>>> on the new node I did the same
>>>
>>> discovery.zen.ping.unicast.hosts: ["host1.mydomain.com:9200"]
>>>
>>> On host1 ESHead says... cluster heath: yellow (24 of 48)
>>> On host2 ESHead says... clusert heath: yellow (1 of 2)
>>>
>>> I see no way to tell that they are attached or that they know about each
>>> other.
>>>
>>> The name of the other node isn't showing up in either version of the
>>> head.
>>>
>>>
>>>
>>>
>>> On Monday, January 26, 2015 at 5:42:44 PM UTC-5, Mark Walkom wrote:
>>>>
>>>> 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 <[email protected]> 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 <[email protected]>
>>>>>>> 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 [email protected].
>>>>>>>> To view this discussion on the web visit
>>>>>>>> https://groups.google.com/d/msgid/elasticsearch/2b89ca10-764
>>>>>>>> a-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 [email protected].
>>>>> 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 [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/elasticsearch/0690924e-d06e-4a94-8f00-58821945aca2%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/elasticsearch/0690924e-d06e-4a94-8f00-58821945aca2%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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/fd89e905-7fea-4672-9579-52f3a915e966%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
