apache / apache/dubbo

instance group in nacos registry always be DEFAULT_GROUP when dubbo.application.register-mode=instance or all

Open
#8,933 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
41.6k
Forks
26.4k
Avg merge
15h 13m
Merged PRs (30d)
4

Description

### Environment

* Dubbo version: 3.0.2
* Operating System version: win10
* Java version: jdk11

### Steps to reproduce this issue

instance group in nacos registry always be DEFAULT_GROUP when `dubbo.application.register-mode=all or instance` and `dubbo.registry.group=dubbo`

```yaml
dubbo:
protocol:
charset: UTF-8
server: netty4
register: true
name: tri
serialization: protostuff
port: -1
provider:
dynamic: true
version: 1.0.0
validation: true
consumer:
validation: true
version: 1.0.0
application:
name: ${spring.application.name}
compiler: javassist
register-mode: all
protocol: tri
# service-discovery:
# migration: FORCE_APPLICATION
registry:
use-as-metadata-center: false
group: dubbo
parameters:
group: dubbo
namespace: ${spring.profiles.active}
```

![image](https://user-images.githubusercontent.com/25682169/134857720-d93a7c2b-ba16-4d3f-816d-74e8564b34fd.png)

![image](https://user-images.githubusercontent.com/25682169/134857783-3925a695-63e9-459d-9ef4-4526bf000e07.png)

### Expected Result

instance group will be dubbo

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by tracing Dubbo 3.0.2's Nacos registry handling for register-mode=all or instance and the registry group parameters; done means instance registrations use the configured dubbo group instead of DEFAULT_GROUP.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.