question-mark
Stuck on an issue?

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.

[Question] Readiness probe should take care of recovery due to connection failures

See original GitHub issue
2020-10-21 05:40:34,817 WARN [Worker clientId=connect-1, groupId=stream-producer-latest-kafka-mysql-connect] Connection to node 2 (ip-10-2-21-191/10.2.21.191:32000) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient) [kafka-coordinator-heartbeat-thread |stream-producer-latest-kafka-mysql-connect]

Today morning for some reason stream producer/kafka connect (kubectl get kc) stopped processing any new request for 60mins. The user reported us the problem then we went and deleted the KC pod and new pod came up and started processing and writing to Kafka.

Can the readiness probe take care of this?

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
scholzjcommented, Oct 21, 2020

I’m afraid there is no PR to follow yet. But this is the approved proposal: https://github.com/strimzi/proposals/blob/master/007-restarting-kafka-connect-connectors-and-tasks.md

0reactions
alok87commented, Oct 21, 2020

Ok thanks any PR/issue i can subscribe.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Configure Liveness, Readiness and Startup Probes
This page shows how to configure liveness, readiness and startup probes for containers. The kubelet uses liveness probes to know when to ...
Read more >
Liveness and Readiness Probes - Red Hat Hybrid Cloud
For a readiness probe, the failureThreshold parameter defines how many times the probe must fail before the pod is removed from the endpoint ......
Read more >
What should readiness & liveness probe actually check for?
The readiness probe must return failure, while the liveness probe must return success. In this way, no new requests are sent to the...
Read more >
How to Troubleshoot and Address Liveness / Readiness ...
Liveness / Readiness probe failures suggest performances issues or slow startup. A quick workaround for such kind of issues is to update those...
Read more >
Liveness Probes are Dangerous | SRCco.de
If you attempt to deploy a change to your application that fails the Liveness/Readiness Probe, the rolling deploy will hang as it waits...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found