Why you need it?
The current client cannot find an available server and directly prints a line of log, ignoring it. The logger does not have a default configuration, making it difficult to troubleshoot the problem.
We need to redefine the behavior here. If the target server cannot be found, the exception will be started directly (it is best to provide a configuration)
当前客户端找不到可用的服务端，是直接打印一行日志，忽略的，logger也没有默认配置，导致排查问题困难。我们需要重新定义这里的行为，找不到目标server，直接启动异常（最好可以提供一个配置）
3条答案
按热度按时间nzkunb0c1#
Currently it is asynchronous to find the server, there is a pr that fails quickly: #6004 , this implementation is a little strange, though, didn't find the server will not fail fast, but when one of the server list is not available, the exception will be thrown out, even if does not affect the use.
目前是异步找server, 有一个快速失败的pr : #6004 , 不过这个实现有一点怪，没发现server并不会快速失败，而是当server列表当中有一个不可用时，异常会抛出来，即使并不影响使用.
ryoqjall2#
oh, thanks ,I think can base 6004 fix. @jsbxyyx
bf1o4zei3#
OK, if the server list is empty, it will fail fast.