yc-22 opened a new issue #11892: URL: https://github.com/apache/shardingsphere/issues/11892
## 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? ShardingSphere 5.0.0-beta ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC ### Expected behavior Write DB operations can perform well when one or several shards are broken as read DB operations. ### Actual behavior It would cause errors and trigger the project's written retry mechanism. Error: Please see the attached error log. ### Reason analyze (If you can) ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. ` spring.shardingsphere.rules.sharding.tables.LedgerEntry.actual-data-nodes: ledger$->{0..3}.LedgerEntry ` - Drop one ledger DB. Then write operation can't perform. - ### 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]
