Dubbo 2.7.1 版本 启动完之后就报错(org.apache.dubbo.remoting.RemotingException: client)

Dubbo 2.7.1 版本 zk也是基于2.7.1版本，版本比较新，百度资源比较少

相关代码

<!-- dubbo Maven 集成依赖-->
<dependency>
    <groupId>org.apache.dubbo</groupId>
    <artifactId>dubbo-spring-boot-starter</artifactId>
    <version>${dubbo.version}</version>
</dependency>
<dependency>
    <groupId>org.apache.dubbo</groupId>
    <artifactId>dubbo</artifactId>
    <version>${dubbo.version}</version>
</dependency>
<dependency>
    <groupId>com.lmax</groupId>
    <artifactId>disruptor</artifactId>
    <version>${disruptor.version}</version>
</dependency>
<dependency>
    <groupId>org.apache.dubbo</groupId>
    <artifactId>dubbo-dependencies-zookeeper</artifactId>
    <version>${dubbo.version}</version>
    <exclusions>
        <!-- 去出slf4j-log4j12 -->
        <exclusion>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-log4j12</artifactId>
        </exclusion>
    </exclusions>
    <type>pom</type>
</dependency>

报错信息

ReconnectTimerTask -  [DUBBO] Fail to connect to HeaderExchangeClient [channel=org.apache.dubbo.remoting.transport.netty4.NettyClient [192.168.1.169:0 -> /192.168.1.5:20888]], dubbo version: 2.7.1, current host: 192.168.1.169
org.apache.dubbo.remoting.RemotingException: client(url: dubbo://192.168.1.5:20888/com.whyl.eems.api.service.city.CityServiceApi?anyhost=true&application=openapi&bean.name=providers:dubbo:com.whyl.eems.api.service.city.CityServiceApi:1.0.0&check=false&codec=dubbo&default.deprecated=false&default.dynamic=false&default.lazy=false&default.register=true&default.sticky=false&deprecated=false&dubbo=2.0.2&dynamic=false&generic=false&heartbeat=60000&interface=com.whyl.eems.api.service.city.CityServiceApi&lazy=false&methods=getHousingTransactionsType,getHousingSelection,getArea,queryByCity,queryByArea&pid=20432&qos.enable=false&register=true&register.ip=192.168.1.169&release=2.7.1&remote.application=user-service&remote.timestamp=1569511690249&revision=1.0.0&side=consumer&sticky=false&timestamp=1569814156202&version=1.0.0) failed to connect to server /192.168.1.5:20888 client-side timeout 3000ms (elapsed: 3002ms) from netty client 192.168.1.169 using dubbo version 2.7.1
    at org.apache.dubbo.remoting.transport.netty4.NettyClient.doConnect(NettyClient.java:136)
    at org.apache.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:186)
    at org.apache.dubbo.remoting.transport.AbstractClient.reconnect(AbstractClient.java:242)
    at org.apache.dubbo.remoting.exchange.support.header.HeaderExchangeClient.reconnect(HeaderExchangeClient.java:152)
    at org.apache.dubbo.remoting.exchange.support.header.ReconnectTimerTask.doTask(ReconnectTimerTask.java:49)
    at org.apache.dubbo.remoting.exchange.support.header.AbstractTimerTask.run(AbstractTimerTask.java:87)
    at org.apache.dubbo.common.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:648)
    at org.apache.dubbo.common.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:727)
    at org.apache.dubbo.common.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:449)
    at java.lang.Thread.run(Thread.java:748)

怎么才能让它不再报错,为什么会出现这样的问题？