I'm thinking organize indexes by type into different nodes, but maybe no sense.
If I use nodes with different machines, how I can ensure all indexes are in same cluster? How I can use a master node on a machine and slaves with another nodes in other machines?
I'm thinking organize indexes by type into different nodes, but maybe no sense.
No, it's hard to see why that would make sense.
If I use nodes with different machines, how I can ensure all indexes are in same cluster? How I can use a master node on a machine and slaves with another nodes in other machines?
You are free to choose exactly which cluster an Elasticsearch node should be a member of so I don't understand your questions.
My doubt is how to make comunications beetween machines with same cluster, and see all nodes with HQ plugin or Kopf plugin installed on "master" machine (node per machine)
Just use regular unicast discovery and configure each node so that it can find at least one other node that's connected to the rest of the cluster. This procedure is the same regardless of whether you run the nodes on the same machine or not.
I have this configurations on two machines: machine 1 is the master, and I want see all indexes of all machines in machine 1.
Here are my configuration for elasticsearch in the machines. At the moment I can't see in machine 1 indexes of machine 2.
Please post your configuration again without all the irrelevant comments (use e.g. sed 's/^ *#.*//; /^$/d' /etc/elasticsearch/elasticsearch.yml) and format your post as code so that it's readable.
Also, have a look in your Elasticsearch log files. It's likely that it contains clues.
With network.host set to 127.0.0.1 or localhost Elasticsearch will only listen on the loopback interface and your two nodes won't be able to contact each other.
So, to each machine maintain communication I have just to comment the line network.host? The configuration in discovery.zen.ping.unicast.hosts is correct?
So, to each machine maintain communication I have just to comment the line network.host?
With ES 2.0 and later I think network.host defaults to localhost so you probably have to set it to e.g. 0.0.0.0 to have it listen on all interfaces. See the release notes. For ES 1.7 and earlier you don't need that setting.
The configuration in discovery.zen.ping.unicast.hosts is correct?
You have the same value for both machines. They should typically point to each other.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.