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

service nacos-cs routed the request to an unavailable instance #425

Open
fyuan1316 opened this issue Jun 21, 2023 · 2 comments · May be fixed by #426
Open

service nacos-cs routed the request to an unavailable instance #425

fyuan1316 opened this issue Jun 21, 2023 · 2 comments · May be fixed by #426

Comments

@fyuan1316
Copy link

release 2.1.1

description:

The nacos cluster is deployed with 3 instances and a power failure causes an abnormal status of 1 instance.
The error is returned by the client requesting /nacos/v1/ns/instance/beat with the configured nacos address
server-addr: nacos-cs。

I think in this case if the readinessProbe check is configured in the statefulset, the unavailable instances will be removed from the service load balancing and this should solve the problem.

I see that there was a discussion #186 about this, and the restart issue described here should have been resolved with the startupProbe. So, if there are no other issues, I think we can add readinessProbe back in.
@fyuan1316 fyuan1316 linked a pull request Jun 21, 2023 that will close this issue
Open
@fyuan1316
Copy link
Author

@paderlol
WDYT ?

@wilsonwu
Copy link
Contributor

Good suggestion.

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

Successfully merging a pull request may close this issue.

Statefulset add readinessProbe fyuan1316/nacos-k8s
2 participants
@wilsonwu @fyuan1316