fcabbage opened a new issue, #15921: URL: https://github.com/apache/dubbo/issues/15921
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Dubbo Version Dubbo: 3.3.0 Java: 1.8 Springboot: 2.7.18 Nacos: 2.x ### Steps to reproduce this issue **Environment**: Kubernetes, Nacos, One Dubbo Provider Pod, One Dubbo Consumer Pod **Deployment Update Strategy**: Rolling update (ensuring at least 1 pod remains available during updates) **Readiness Probe Configuration**: ``` readinessProbe: failureThreshold: 3 httpGet: path: /ready port: 22222 scheme: HTTP initialDelaySeconds: 5 periodSeconds: 2 successThreshold: 1 timeoutSeconds: 1 ``` During the rolling upgrade of the Dubbo Provider, I found that there are so many "no provider" error, the key timelines: - Provider registered to Nacos: 17:59:18 - Consumer first encountered "**no provider**" error: 17:59:20 - Connection established between Consumer and new Provider: 18:00:03 I understand that adjusting probe parameters (e.g., increasing successThreshold or periodSeconds) might mitigate this issue. However, the time gap between "Provider registration to Nacos" and "Actual Connection Established" is unpredictable in practice. **Core Question**: Are the Dubbo QOS /ready /live endpoints designed to be compatible with Kubernetes liveness/readiness probes? If not, is there an official recommendation for Dubbo applications to implement Kubernetes-native health checks? ### What you expected to happen I hope the community can provide appropriate recommendations for Kubernetes probes to the Dubbo applications. ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [ ] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
