typefield commented on issue #15554:
URL: https://github.com/apache/dubbo/issues/15554#issuecomment-4824346655
I tried to reproduce this today with a local Nacos 3.0.2 standalone server
and the released Dubbo versions mentioned in this issue, but I could not
reproduce the startup failure in the default setup.
What I tested:
- Nacos Server 3.0.2 release tarball, standalone mode, API port `8082`
- Dubbo 3.3.0: `dubbo-configcenter-nacos` resolves
`com.alibaba.nacos:nacos-client:2.4.1`
- Dubbo 3.3.5: `dubbo-configcenter-nacos` resolves
`com.alibaba.nacos:nacos-client:2.5.1`
- Directly initialized Dubbo's Nacos config-center, metadata-report and
registry code paths against `nacos://127.0.0.1:8082`
Result:
```text
Dubbo 3.3.0:
config-center=OK
metadata-report=OK
registry=OK
Dubbo 3.3.5:
config-center=OK
metadata-report=OK
registry=OK
```
I also verified that Nacos 3.0.2 does return `410 Gone` for the old admin
API:
```text
GET /nacos/v1/ns/operator/switches -> 410 Gone
```
However, in this environment the Nacos client status check did not use that
endpoint for `getServerStatus()`. The client-side status endpoint observed in
the access log was:
```text
GET /nacos/v1/ns/operator/metrics -> 200 {"status":"UP"}
```
I also checked several Nacos client versions directly (`1.4.1`, `1.4.2`,
`1.4.6`, `1.4.7`, `2.0.4`, `2.1.2`, `2.2.4`, `2.3.2`, `2.4.1`, `2.5.1`,
`2.5.2`); all returned `getServerStatus=UP` and real config/naming requests
succeeded against the default Nacos 3.0.2 server.
Tentative conclusion: the removal of `/v1/ns/operator/switches` is real, but
I cannot confirm that it alone causes Dubbo 3.3.0/3.3.5 startup failure with
the default released dependency set. This may depend on extra environment
details such as an overridden `nacos-client` version, Nacos compatibility
flags, auth/security settings, reverse proxy behavior, or port mapping.
Could someone who can reproduce this share:
1. `mvn dependency:tree -Dincludes=com.alibaba.nacos:nacos-client`
2. The relevant Nacos 3.x `application.properties` API compatibility settings
3. Whether the Nacos client gRPC port is reachable from the Dubbo process
4. A minimal runnable sample if possible
With those details we can decide whether Dubbo needs a fallback around
`getServerStatus()` or whether this is caused by a specific
Nacos/client/environment combination.
--
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]
