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 and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

use dubbo-spring-boot-starter and dubbo-nacos-spring-boot-starter ,version is 3.3.5

Steps to reproduce this issue

1.I have a remote config , in nacos ,version 2.1.0.2, remote config properties

dubbo.config-center.highest-priority=false dubbo.service.register=false

What you expected to happen

In my local configuration file, the configuration is dubbo.service.register=true, but it is overwritten by the remote configuration. Until I declare dubbo.config-center.highest-priority=false locally, the local configuration will not be overwritten.

So, my question is, even if the remote configuration is also dubbo.config-center.highest-priority=false, if the local does not also declare dubbo.config-center.highest-priority=false, the local configuration will still be overwritten by the remote

Anything else

No response

Are you willing to submit a pull request to fix on your own?

  • [x] Yes I am willing to submit a pull request on my own!

Code of Conduct

Comment From: ArjunDixit1

Pls assign me this @zrlw my thought process is the remote highest-priority=false setting in Nacos itself is applied with the default true priority, making it ineffective in this scenario. You must declare it locally to change the default behavior for the remote configuration source. Setting dubbo.config-center.highest-priority=false in your local configuration file is the correct way to solve this. It explicitly instructs Dubbo to treat the remote configuration from Nacos as having a lower priority than your local properties, preventing the local dubbo.service.register=true from being overwritten.