etcd in bound message size out of limit when starting shardingsphere

[roodkcab]

Bug Report

Which version of ShardingSphere did you use?

master

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

proxy

Expected behavior

cluster mode with etcd should start without problem

Actual behavior

fail to start with exception

Exception in thread "main" java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: gRPC message exceeds maximum size 4194304: 5358489
        at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
        at org.apache.shardingsphere.mode.repository.cluster.etcd.EtcdRepository.getChildrenKeys(EtcdRepository.java:85)
        at org.apache.shardingsphere.mode.metadata.persist.service.SchemaMetaDataPersistService.loadAllNames(SchemaMetaDataPersistService.java:86)
        at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.beforeBuildContextManager(ClusterContextManagerBuilder.java:96)
        at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.build(ClusterContextManagerBuilder.java:82)
        at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.initContext(BootstrapInitializer.java:77)
        at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.init(BootstrapInitializer.java:68)
        at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:47)

Reason analyze (If you can)

there are about 1300 tables in a single database, when get all of metadata from etcd, the in bound message size out of limit.