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

Retry for endpoint detection #1939

Open
erikpetzold opened this issue Jan 14, 2022 · 2 comments
Open

Retry for endpoint detection #1939

erikpetzold opened this issue Jan 14, 2022 · 2 comments

Comments

@erikpetzold
Copy link
Member

When endpoint detection fails (e.g. due to network issues), then SBA will not know about the endpoints of that instance and there is no option to trigger the detection again. The current solution would be restarting the instance.

Endpoints should not change while the application is running, so we do not need a periodic trigger or a button in the ui. Only in error case there should be a retry. See ProbeEndpointsStrategy.

@pasolid
Copy link

pasolid commented Jan 30, 2022

Maybe some management button with "Forget instance" functionality. I have similar issue in Kubernetes. I use client discovery to locate all services and their endpoints, but if fo some reason service is redeployed then SBA keeps trying to connect the old one.
I get the rationale behind this behavior, but I would still prefer to have an option/manual control to tell SBA to forget current instance and try to locate another (to trigger rediscovery of service)

@SteKoe
Copy link
Contributor

SteKoe commented Dec 23, 2024

We have implemented a button to retrigger service detection to the UI, it will be shipped with the next release. It allows users to manually retry detection when implemented discovery clients have some issues detecting running services (e.g. consul).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants