guodongym commented on issue #10413: URL: https://github.com/apache/dolphinscheduler/issues/10413#issuecomment-1159477490
> @guodongym Could you please provide more detail? Which version? And what exception, right now in dev branch, if the master cannot connect to zookeeper or database in startup, it will stop. > > But if the database connect failed in running, this does happen, do you have any good idea, I think we can sleep here if we check the exception generated is too faster in the loop. > > We need to add specific exception and metrics about the exception. The problem I found was that the constructor threw an exception during the initialization phase of the bean, so that the data source connection would not be initialized, so that the real exception would not be seen. I was wondering if I could catch some unrecoverable exceptions to break the loop 我发现的问题现象是启动初始化bean的阶段，构造方法抛出异常，导致数据源连接还没初始化，就会一直刷报错日志，导致真正的异常也被刷掉看不到了，我在想是不是可以捕捉某些不可恢复的异常让循环中断  -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
