qxggg commented on issue #15554: URL: https://github.com/apache/dubbo/issues/15554#issuecomment-3587218253
Hi all, I’ve tracked down the root cause of the issue: in our Maven setup, Dubbo is still referencing Nacos 2.x. As a result, Dubbo relies on the old serverStatus endpoint to check the health of Nacos servers. In Nacos 3.x, this endpoint has been removed and now returns 410 Gone, which causes Dubbo to incorrectly mark the server as DOWN. Given this, I’d like to ask: for the next version of Dubbo, should we consider adding official support or adaptation for Nacos 3.x? This would ensure compatibility with the new Nacos API while preserving the health check and dynamic configuration features. Finally, I create an issue in the nacos repository : https://github.com/alibaba/nacos/issues/13984 Thanks! <img width="628" height="196" alt="Image" src="https://github.com/user-attachments/assets/e0b20c91-b224-44cf-b8fa-8c0d9d98f74e"; /> -- 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]
