asadjan4611 commented on issue #17985: URL: https://github.com/apache/dolphinscheduler/issues/17985#issuecomment-3943182906
You’re right to point this out. My concern is mainly the operational impact when the DB/table check fails due to transient startup conditions (for example short DB unavailability), because `System.exit(1)` immediately terminates the process. If you agree, I can prepare a small PR that keeps the current validation logic but replaces hard exit with a controlled failure path (clear error message + graceful stop/retry-friendly behavior), so it is safer in production environments. -- 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]
