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.

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

[bitnami/kafka] Liveness probe not effectively finding failed pods #31119

Open
igloo12 opened this issue Dec 19, 2024 · 2 comments
Open

[bitnami/kafka] Liveness probe not effectively finding failed pods #31119

igloo12 opened this issue Dec 19, 2024 · 2 comments
Assignees
Labels
kafka stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@igloo12
Copy link

igloo12 commented Dec 19, 2024

Name and Version

bitnami/kafka:30.1.0

What architecture are you using?

None

What steps will reproduce the bug?

  1. Use default helm chart
  2. A node will fail it's readiness check
  3. Liveness probe doesn't not fail until hours later

Are you using any custom parameters or values?

No response

What is the expected behavior?

Liveness probe fails after reasonable time

What do you see instead?

Bad pod is kept alive too long blocking kafka from healing

Additional information

Why is the liveness probe different from readiness? Checking if the kafka process is alive doesn't mean it is healthy. Related to issue 31100 once the pod goes down it takes hours to restart the pod

@igloo12 igloo12 added the tech-issues The user has a technical issue about an application label Dec 19, 2024
@github-actions github-actions bot added the triage Triage is needed label Dec 19, 2024
@carrodher
Copy link
Member

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

Copy link

github-actions bot commented Jan 8, 2025

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kafka stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants