[Bug] [DUBBO] Failed to publish service name mapping to metadata center by cas operation.

[tom055]

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

version:3.2.17

dubbo provider can't register into redis
pom.xml

<dependency>
            <groupId>org.apache.dubbo</groupId>
            <artifactId>dubbo-spring-boot-starter</artifactId>
        </dependency>
        <dependency>
            <groupId>org.apache.dubbo</groupId>
            <artifactId>dubbo</artifactId>
        </dependency>
<dependency>
            <groupId>org.apache.dubbo.extensions</groupId>
            <artifactId>dubbo-registry-redis</artifactId>
        </dependency>

application.yml

server:
  port: 8822
spring:
  application:
    name: db-provider
dubbo:
  scan:
    base-packages: org.example.provider.service
  registry:
    address: redis://127.0.0.1:6379
    protocol: redis
    parameters:
      db.index: 0
    cluster: failover
  protocol:
    id: dubbo-protocol
    name: dubbo
    port: 20882
  application:
    qos-enable: false
  provider:
    version: 1.0.0
  consumer:
    version: 1.0.0

ApiOrderImpl.java

package org.example.provider.service;

import org.apache.dubbo.config.annotation.DubboService;
import org.example.api.model.OrderPo;
import org.example.api.service.ApiOrder;

@DubboService(version = "1.0.0",protocol = {"dubbo"},cluster="failfast")
public class ApiOrderImpl implements ApiOrder {
    @Override
    public OrderPo apply(OrderPo po) {
        po.setCount(po.getCount() + 1);
        return po;
    }
}

2025-04-08T11:00:12.689+08:00  INFO 23984 --- [db-provider] [           main] org.apache.dubbo.metadata.MetadataInfo   :  [DUBBO] metadata revision changed: null -> 486fa0122461d734d2c9e496ea1ef4f3, app: db-provider, services: 1, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:12.693+08:00  INFO 23984 --- [db-provider] [           main] org.example.provider.App                 : Started App in 281.424 seconds (process running for 281.81)
2025-04-08T11:00:17.653+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] Try to register interface application mapping for service org.example.api.service.ApiOrder:1.0.0, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:18.802+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 1. Next retry delay: 14. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:19.305+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 2. Next retry delay: 61. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:19.430+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 3. Next retry delay: 61. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:19.566+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 4. Next retry delay: 27. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:19.635+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 5. Next retry delay: 4. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:19.686+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 6. Next retry delay: 43. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:19.777+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 7. Next retry delay: 28. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:19.847+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 8. Next retry delay: 60. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:19.958+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 9. Next retry delay: 5. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:20.008+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 10. Next retry delay: 70. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:20.135+08:00  INFO 23984 --- [db-provider] [eduler-thread-4] o.a.d.r.c.m.MetadataServiceNameMapping   :  [DUBBO] Failed to publish service name mapping to metadata center by cas operation. Times: 11. Next retry delay: 53. Service Interface: org.example.api.service.ApiOrder. Origin Content: null. Ticket: null. Excepted context: db-provider, dubbo version: 3.2.17, current host: 192.168.56.1
2025-04-08T11:00:20.188+08:00 ERROR 23984 --- [db-provider] [eduler-thread-4] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] Failed register interface application mapping for service org.example.api.service.ApiOrder:1.0.0, dubbo version: 3.2.17, current host: 192.168.56.1, error code: 5-10. This may be caused by configuration server disconnected, go to https://dubbo.apache.org/faq/5/10 to find instructions. 

Steps to reproduce this issue

can't register into redis

What you expected to happen

RedisMetadataReport not achieve registerServiceAppMapping this method

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

• I agree to follow this project's Code of Conduct

[Stellar1999]

This issue can be raised in dubbo-spi-extensions.
https://github.com/apache/dubbo-spi-extensions