apache/dubbo

[Bug] Dubbo 3.3.5 fails to start with Nacos 3.x due to removed /v1/ns/operator/switches API

Open

#15554 opened on Jul 15, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (41,524 stars) (26,453 forks)batch import
help wantedstatus/waiting-for-feedbacktype/enhancement

Description

Pre-check

  • I am sure that all the content I provide is in English.

Search before asking

  • I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

Item Version
Dubbo 3.3.0
Nacos Server 3.0.2
JDK openjdk-17
OS Windows

Steps to reproduce this issue

1.Start Nacos 3.0.2 in standalone mode: docker run -d -p 8082:8848 -p 8083:9848
-e MODE=standalone nacos/nacos-server:3.0.2 Configure Dubbo application.yml: dubbo: config-center: address: nacos://localhost:8082 registry: address: nacos://localhost:8082 metadata-report: address: nacos://localhost:8082 Start the Dubbo application.

What you expected to happen

Application starts successfully with logs: Successfully connected to nacos config server ...

Anything else

Actual Behavior Logs repeatedly print: Failed to connect to nacos config server. Server status: DOWN. Config Service Available: true. Root Cause Dubbo uses GET /nacos/v1/ns/operator/switches to determine the server status. Nacos 3.x has removed this endpoint and returns 410 Gone, causing Dubbo to treat the server as DOWN.

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

Contributor guide

Tech stack
java
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaDubboNacosDocker
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the Dubbo Nacos integration code to find where GET /nacos/v1/ns/operator/switches is called (likely in the NacosRegistry or NacosMetadataReport class). The endpoint was removed in Nacos 3.x, returning 410. A fix could involve catching this response and treating the server as UP, or using an alternative endpoint like /nacos/v1/ns/service/list to verify server status. Look at the Nacos client library for a health check API. Check the repository's test cases for Nacos integration to ensure compatibility.