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

Implementing Dependency-Responsive Liveliness Probes in Frontend Pod #442

Open
ziemowit141 opened this issue Nov 10, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@ziemowit141
Copy link

Is your feature request related to a problem? Please describe.

We have identified a critical issue in our system architecture related to service interdependencies. Specifically, this problem arises when the matching pod encounters a failure, leading to a disruption in the connection. This disruption necessitates a manual restart of the frontend pod. The reason behind this is that the connections to dependent services are initialized during the startup phase of the frontend pod. Consequently, any interruption in these services post-launch results in the following error:

If that happens then we get this error:
Screenshot 2023-11-10 at 12 42 35

Describe the solution you'd like

To mitigate this issue, we propose the implementation of advanced liveliness probes within the frontend pod. These probes will be responsible for continuously monitoring the health status of all dependent services. In the event of a service failure, these probes will automatically initiate a restart of the frontend pod, thereby restoring the system's operational status without manual intervention.

Additional context

I'm not sure about the root-cause of matching pod failing, if I establish that I will add those details to the issue.

@ziemowit141 ziemowit141 added the enhancement New feature or request label Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant