elasticsearch_client health check keeps failing, redeploying in marathon
See original GitHub issueAfter ELK addon is installed (via ansible), seeing the following:
Marathon -
Warning: Health check 'HTTP /_cluster/health' failed.
I also tried this with the steps provided in #1318, got the same error.
- Ansible version (
ansible --version
): 1.9.4 - Python version (
python --version
): 2.7.5 - Git commit hash or branch: master:latest
- Cloud Environment: GCE
- Terraform version (
terraform version
): 0.6.13
Issue Analytics
- State:
- Created 7 years ago
- Comments:18 (7 by maintainers)
Top Results From Across the Web
ElasticSearch health check failed every time when spring boot ...
client.RestClient but I was using org.elasticsearch.client.RestHighLevelClient and had created Bean for the same. In case you want to keep ...
Read more >2.1 Elasticsearch health check failures · Issue #16007 - GitHub
The health indicator uses each RestClient bean in the application context. It's failing because the connection is being refused. That suggests ...
Read more >Elasticsearch Healthcheck failure w/ Spring Boot
I posted on an issue on the spring boot GitHub, and was referred here. I will try to make this is simple as...
Read more >代码 Issues - Gitee
Keep you config structs along with the code they configure and delegate parsing to submodules without sacrificing full config serialization.
Read more >Praxis - OSCHINA - 中文开源技术交流社区
The Identifier that appears in the DeclaratorId may be used as a simple name in the body of the method or constructor to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@distributorofpain You’ll want to run a
curl
command, that’s what Consul is doing. I think thatshould do it, where
<your-node>
is the IP address you got from the Marathon dashboard, as @ryane mentioned.Since this issue has been unreproducable, I’m going to close this. If anyone sees it again, please reopen!