New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ec2-discovery not configured correctly at network.host #46
Comments
Using 0.0.0.0 will make the node accept traffic on public IPs and that is not recommended How exactly does removing localhost help? can you point to the relevant documentation? |
I agree that it's not recommended. Binding it to localhost result in only 127.0.0.1:9200 which result in hosts not able to ping each other. |
This is why we bind to both I will not change the bind host to 0.0.0.0. |
I've found the real issue. It should grab the correct endpoint if it's not set, however, due to open issue it does not. |
That is incorrect. You should have set the variables correctly. Please follow the README. https://github.com/synhershko/elasticsearch-cloud-deploy/tree/master/terraform-aws#configurations |
Sorry, reading this again it seems like we are better adding the |
Current configuration provided in the user-data for the network.host is:
network.host: ec2:privateIpv4,localhost
This cause the client node not to see the other nodes in the cluster with the following error:
[o.e.d.z.ZenDiscovery ] [Elasticsearch-Master] not enough master nodes discovered during pinging.
Removing the localhost and adding ec2.endpoint partially resolves this issue, now the client node is able to ping all the masters however on Kibana it is reported that it cannot access elasticsearch on http://localhost:9200.
To solve this, on the client node I had to change it from ec2:privateIpv4 to 0.0.0.0 and everything started to work.
The text was updated successfully, but these errors were encountered: