-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FailoverReactor did not stop when spring application failed to start #3161
Comments
Can you use new version to have a try? |
No response more than 7 days, close issue |
I have the same problem, and it doesn’t happen every time. It is normal after restarting the service nacos-client 1.2.1 INFO log stops at the following location
After modifying the log level to DEBUG, you can see the following log
|
I have the same problem |
solved, just update the version |
Issue Description
Type: bug report
nacos
FailoverReactor
did not stop when spring application failed to startmy application always print logs when app failed to start
12:00:33.223 [com.alibaba.nacos.naming.failover] DEBUG com.alibaba.nacos.client.naming.run - failover switch is not found, failover00-00---000-VIPSRV_FAILOVER_SWITCH-000---00-00
12:00:38.223 [com.alibaba.nacos.naming.failover] DEBUG com.alibaba.nacos.client.naming.run - failover switch is not found, failover00-00---000-VIPSRV_FAILOVER_SWITCH-000---00-00
12:00:43.224 [com.alibaba.nacos.naming.failover] DEBUG com.alibaba.nacos.client.naming.run - failover switch is not found, failover00-00---000-VIPSRV_FAILOVER_SWITCH-000---00-00
12:00:48.225 [com.alibaba.nacos.naming.failover] DEBUG com.alibaba.nacos.client.naming.run - failover switch is not found, failover00-00---000-VIPSRV_FAILOVER_SWITCH-000---00-00
12:00:53.226 [com.alibaba.nacos.naming.failover] DEBUG com.alibaba.nacos.client.naming.run - failover switch is not found, failover00-00---000-VIPSRV_FAILOVER_SWITCH-000---00-00
...
How to reproduce it (as minimally and precisely as possible)
Tell us your environment
Anything else we need to know?
i use supervisor to start the app, the status is always running even app failed to start
The text was updated successfully, but these errors were encountered: