I used this method to create Elastic Search clusters in the cloud. It works in 30-50% of cases.
I start with 2 centos nodes on 2 servers in Digital Oceans Cloud. Then I install ES and set the same cluster name in each config / elasticsearch.yml. Then I also install (uncomment):
discovery.zen.ping.multicast.enabled: false
as well as install and uncomment:
discovery.zen.ping.unicast.hosts: ['192.168.10.1:9300', '192.168.10.2:9300']
on each of the two servers. SO link here
Then, to give ES the advantage of doubt, I service iptables stop, then restart the service on each node. Sometimes the servers see each other, and I get the "cluster" from "elasticsearch, sometimes, if not in the majority, the servers do not see each other, even if the multicast is disabled and the specific IP addresses are listed in the array of unicast hosts that have NO firewall and point to each other.
WHY ES Community? Why the global equivalent of elastic search is still inelastic (let me openly and readily admit that it MUST be a user error / idiocy, otherwise no one will use this technology).
4 node, , , , , . 0% . ( ), " " " ". googled , / .
- , , ?
@Ben_Lim : , ? 1 node ( Prod) Server1 /config/elasticsearch.yml:
uncomment node.master: true
network.host: 192.XXX.1.10
uncomment transport.tcp.port: 9300
uncomment discovery.zen.ping.multicast.enabled: false
uncomment set discovery.zen.ping.unicast.hosts: [ "192.XXX.1.10: 9300" ]
, , node ( ), -
uncomment node.master: false
network.host: 192.XXX.1.11
uncomment transport.tcp.port: 9301
uncomment discovery.zen.ping.multicast.enabled: false
uncomment set discovery.zen.ping.unicast.hosts: [ "192.XXX.1.10: 9300" ]
, , , iptables .. .
NOTE AGAIN -- This is not for prod, but a way to start testing ES in Cloud, you can tighten up the screws from here