apache/dubbo

the Configuration `Cluster` and `retries` on `<dubbo:service/>` doesn't work

Open

#15668 opened on Sep 3, 2025

View on GitHub
 (6 comments) (0 reactions) (1 assignee)Java (41,524 stars) (26,453 forks)batch import
help wanted

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

Based on the official doc, we can set cluster and retries on the provider side <dubbo:service/>.

But it doesn't work when I set them on the provider side. The consumer is still using the default failover cluster. Is this feature still functional?

Steps to reproduce this issue

Add cluster or retries to the privder service.

What you expected to happen

<dubbo:service cluster="failsafe" /> shoud work

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

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.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaDubbo configurationXML configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the configuration propagation from `<dubbo:service>` provider side to consumer. Examine the source code in ServiceConfig or related classes to see how `cluster` and `retries` are parsed and applied. Reproduce the issue with a minimal setup and trace the configuration flow. Check official documentation and any related issues.