You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
com.alibaba.nacos.naming.core.v2.upgrade.doublewrite.delay.ServiceChangeV1Task.ServiceChangeV1TaskProcessor#transfer
serviceV2.groupName is coming from serviceV1.groupName
However, serviceV1.groupName are always DEFAULT_GROUP when sync from other server, see com.alibaba.nacos.naming.consistency.ephemeral.distro.DistroConsistencyServiceImpl#processData(byte[]):
Loggers.DISTRO.info("creating service {}", entry.getKey());
Service service = new Service();
String serviceName = KeyBuilder.getServiceName(entry.getKey());
String namespaceId = KeyBuilder.getNamespace(entry.getKey());
service.setName(serviceName);
service.setNamespaceId(namespaceId);
service.setGroupName(Constants.DEFAULT_GROUP); // <----- here
Expected behavior
Using NamingUtils.getGroupName(service.getName()) first to get groupName.
The text was updated successfully, but these errors were encountered:
Describe the bug
com.alibaba.nacos.naming.core.v2.upgrade.doublewrite.delay.ServiceChangeV1Task.ServiceChangeV1TaskProcessor#transfer
serviceV2.groupName
is coming fromserviceV1.groupName
However, serviceV1.groupName are always DEFAULT_GROUP when sync from other server, see
com.alibaba.nacos.naming.consistency.ephemeral.distro.DistroConsistencyServiceImpl#processData(byte[])
:Expected behavior
Using
NamingUtils.getGroupName(service.getName())
first to get groupName.The text was updated successfully, but these errors were encountered: