关于nacos无限刷日志的问题解决过程

情况1：
https://www.jianshu.com/p/37b9719c1191
这一篇是在Linux下启动的Nacos，然后，解决办法是，给Nacos服务指定固定IP
但是，对我的情况无效

情况2：
https://blog.csdn.net/nklinsirui/article/details/108341845
说是Nacos版本的bug，于是，升级nacos服务即可
我也升级了，但是无效

我的情况：
我在springboot配置文件中，设置了Nacos连接的账号密码

  cloud:
    nacos:
      discovery:
        server-addr: 127.0.0.1:8848
        namespace: ${NACOS_SPACE:public}
        username: ${NACOS_USERNAME:nacos}
        password: ${NACOS_PASSWORD:nacos}

所以，导致不停的刷取配置
控制台信息如下：

01-22 12:58:24:068  INFO 30020 --- [extShutdownHook] o.s.s.c.ThreadPoolTaskScheduler          : Shutting down ExecutorService 'Nacos-Watch-Task-Scheduler'
01-22 12:58:24:070  INFO 30020 --- [extShutdownHook] c.a.c.n.registry.NacosServiceRegistry    : De-registering from Nacos Server now...
01-22 12:58:24:071  INFO 30020 --- [extShutdownHook] com.alibaba.nacos.client.naming          : [BEAT] removing beat: DEFAULT_GROUP@@userservice:192.168.31.189:8082 from beat map.
01-22 12:58:24:071  INFO 30020 --- [extShutdownHook] com.alibaba.nacos.client.naming          : [DEREGISTER-SERVICE] public deregistering service DEFAULT_GROUP@@userservice with instance: Instance{instanceId='null', ip='192.168.31.189', port=8082, weight=1.0, healthy=true, enabled=true, ephemeral=true, clusterName='DEFAULT', serviceName='null', metadata={}}
01-22 12:58:24:078  INFO 30020 --- [extShutdownHook] c.a.c.n.registry.NacosServiceRegistry    : De-registration finished.
01-22 12:58:24:078  INFO 30020 --- [extShutdownHook] com.alibaba.nacos.client.naming          : com.alibaba.nacos.client.naming.beat.BeatReactor do shutdown begin
01-22 12:58:24:245  INFO 30020 --- [0.1_8848-public] c.a.n.client.config.impl.ClientWorker    : [fixed-127.0.0.1_8848-public] [polling-resp] config changed. dataId=userservice-dev.yaml, group=DEFAULT_GROUP, tenant=public
01-22 12:58:24:246  INFO 30020 --- [0.1_8848-public] c.a.n.client.config.impl.ClientWorker    : get changedGroupKeys:[userservice-dev.yaml+DEFAULT_GROUP+public]
01-22 12:58:24:271  INFO 30020 --- [0.1_8848-public] c.a.n.client.config.impl.ClientWorker    : [fixed-127.0.0.1_8848-public] [data-received] dataId=userservice-dev.yaml, group=DEFAULT_GROUP, tenant=public, md5=1b0c284b445350f667b41fe8ca48d700, content=pattern:
    dateformat: yyyy-MM-dd HH:mm:ss
    info: text info, type=yaml
01-22 12:58:24:445  INFO 30020 --- [0.1_8848-public] c.a.n.client.config.impl.ClientWorker    : [fixed-127.0.0.1_8848-public] [polling-resp] config changed. dataId=userservice-dev.yaml, group=DEFAULT_GROUP, tenant=public
01-22 12:58:24:446  INFO 30020 --- [0.1_8848-public] c.a.n.client.config.impl.ClientWorker    : get changedGroupKeys:[userservice-dev.yaml+DEFAULT_GROUP+public]
01-22 12:58:24:464  INFO 30020 --- [0.1_8848-public] c.a.n.client.config.impl.ClientWorker    : [fixed-127.0.0.1_8848-public] [data-received] dataId=userservice-dev.yaml, group=DEFAULT_GROUP, tenant=public, md5=1b0c284b445350f667b41fe8ca48d700, content=pattern:
    dateformat: yyyy-MM-dd HH:mm:ss
    info: text info, type=yaml
01-22 12:58:24:566  INFO 30020 --- [extShutdownHook] com.alibaba.nacos.client.naming          : com.alibaba.nacos.client.naming.beat.BeatReactor do shutdown stop
01-22 12:58:24:567  INFO 30020 --- [extShutdownHook] com.alibaba.nacos.client.naming          : com.alibaba.nacos.client.naming.core.HostReactor do shutdown begin

于是，我去除 namespace 的设置，就解决消除了这个情况
但是，这不是最终办法
应该保证在设置 namespace 和不设置 namespace 的两种情况下
都不会出现刷配置的情况。
有待进一步解决。