Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Liveness probe for REST Pod should be switched off
See original GitHub issueIn the TP3 release of Syndesis, both readiness and liveness probes continue to cause the REST pod to restart and redeploy. Below are the log entries arising from the probe.
5:26:57 PM | Warning | Unhealthy | Readiness probe failed: Get http://10.1.7.122:8181/health: dial tcp 10.1.7.122:8181: getsockopt: connection refused28 times in the last 10 minutes -- | -- | -- | --
5:25:07 PM | Warning | Unhealthy | Liveness probe failed: Get http://10.1.7.122:8080/api/v1/version: dial tcp 10.1.7.122:8080: getsockopt: connection refused
These health checks are unnecessary and only causes long wait times for creation and testing of integrations.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Liveness probes are important and essential for proper self-healing. So we should tackle this for sure (i suspect some spring-boot percularities here).
wrt. to OOM error, we should (a) investigate our configured limits and (b) verify that we dont have a memory leak.
We’re getting awful experience because of pod restarts due to liveness probes. We should either remove them or configure them correctly.
Let me dial in some OpenShift/Kubernetes support by calling @chirino, @iocanel and @rhuss for help.