-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Routed target zta_execution_detail_19
does not exist, available targets are `[zta_execution_0....
#28994
Comments
It should be caused by concurrency. This problem is more likely to be triggered when my system has a large number of requests. |
i hava this error too |
i have got the same problem, but when i send request once more, This bug is not stable complex is now |
@lenxeon Can you give a demo to help reproduce this exception? |
in my project, It is low probability randomness, when i send request once more, it is running ok. |
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
I also encountered the same exception, the difference is that I used it in Datax, because Datax also executes tasks in multiple threads, so I think the error is the same as yours |
This is my config file
|
Bug Report
Which version of ShardingSphere did you use?
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
Correct routing to the correct shard table
Actual behavior
Occasionally the wrong routing rule is used, most of the time it's normal
The logical table of zta_execution_detail_19 is zta_execution_detail, but the ‘available targets’ in the error log is zta_execution.
Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
This is my configuration class.
Maybe it's related to concurrency? Or do I need to modify my configuration?
Example codes for reproduce this issue (such as a github link).
The text was updated successfully, but these errors were encountered: