Elasticsearch Cluster - Unknown node wizard, repeat planning

Question

I have a server running elasticsearch and kibana. I added a second node to create the cluster, but I want the second node to replicate data from the node wizard.

Based on the limited documentation on how to do this, I start at the second moment with the following error

[DEBUG][action.admin.indices.get ] [Match] no known master node, scheduling a retry 

I cannot determine the best configuration for both servers to achieve this, but this is what I have done so far:

Node wizard Configuration:

 cluster.name: elasticsearch node.master: true path.data: /local00/elasticsearch/ path.work: /local00/el_temp/ network.host: 0.0.0.0 http.port: 9200 script.disable_dynamic: true 

Node 2

 cluster.name: elasticsearch node.master: false node.data: true index.number_of_shards: 5 index.number_of_replicas: 1 path.data: /local00/elasticsearch/ path.work: /local00/el_temp/ network.host: 0.0.0.0 http.port: 9200 script.disable_dynamic: true 

I assume that somewhere there is no additional configuration. Any help would be greatly appreciated.

Answer 1

Did he get to work with the following changes listed here How to set up an ES cluster? :

Node 1:

 cluster.name: mycluster node.name: "node1" node.master: true node.data: true discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["node1.example.com"] 

Node 2:

 cluster.name: mycluster node.name: "node2" node.master: false node.data: true discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["node1.example.com"] 

Answer 2

If you are trying to connect an additional node to an existing ES cluster, make sure that this node also has the same ES plugins as other nodes. If not, node cannot be fully connected (other nodes can show it as connected, but HTTP commands cannot be run on it) to the ES cluster with an error, for example:

 [2016-07-21 11:56:59,564][DEBUG][action.admin.cluster.health] [dev-marvel1] no known master node, scheduling a retry [2016-07-21 11:57:05,313][INFO ][rest.suppressed ] /_cluster/health Params: {pretty=true} MasterNotDiscoveredException[waited for [30s]] at org.elasticsearch.action.support.master.TransportMasterNodeAction$4.onTimeout(TransportMasterNodeAction.java:154) at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:239) at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:574) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) 

In my case, the problem was with the license plugin. After removal, everything became good.