sccc803 opened a new issue #11468: URL: https://github.com/apache/shardingsphere/issues/11468
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? 5.0.0-RC1-SNAPSHOT ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior ExecutorService is supposed to shutdown for process to exit when loading table meta data failed. ### Actual behavior ExecutorService does not shutdown when loading table meta data failed, that causes the process to not exit correctly. ### Reason analyze (If you can)  When a task calling loadTableByDataNode failed, the exception will be thrown resulting in ExecutorService cannot shutdown. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1. Set the property check-table-metadata-enabled to true 2. Create scenarios where calling loadTableByDataNode failed. ### Example codes for reproduce this issue (such as a github link). -- 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]
