Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Kafkaconnect does not auto recover on failures #121

Open
alok87 opened this issue Nov 27, 2020 · 1 comment
Open

Kafkaconnect does not auto recover on failures #121

alok87 opened this issue Nov 27, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@alok87
Copy link
Contributor

alok87 commented Nov 27, 2020

Kubernetes is designed to restart stuffs if they fail, for them to recover. Though we need to look at why it failed but a failure which lies as failed is more of problem and k8s restart does help.

Strimzi's KafkaConnect does not implement any probes, here is a discussion. strimzi/strimzi-kafka-operator#3850

We should do something for k8s restart to take effect if it cannot be done from Strimzi. It is very much required
@alok87 alok87 added the bug Something isn't working label Mar 18, 2021
@alok87 alok87 mentioned this issue May 2, 2021
Merged
@alok87
Copy link
Contributor Author

alok87 commented Feb 12, 2022 •
edited

Need to explore strimzi/strimzi-kafka-operator#4114

strimzi now supports restarting connectors!

Related: strimzi/strimzi-kafka-operator#2621

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alok87