Open 6westboy9 opened 6 months ago
Hi @6westboy9 , migration and check will create internal Standalone data source, that's ok.
From SHOW MIGRATION CHECK STATUS
, looks check job is still running, you could try to verify it on underlying MySQL show processlist
.
Bug Report
When I used ShardingSphere-Proxy for data migration, I found that the migration was normal, but the validation could not be performed, and the error message was as follows:
cat ${ShardingSphere-Proxy-HOME}/logs/stdout.log![image](https://github.com/apache/shardingsphere/assets/39526241/2d75cd7b-09a1-482f-90cc-5f4e76275baf)
ShardingSphere-Proxy server configuration is as follows:
cat ${ShardingSphere-Proxy-HOME}/conf/server.yaml
Which version of ShardingSphere did you use?
apache-shardingsphere-5.4.1-shardingsphere-proxy-bin.tar.gz
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
Expected behavior
Successfully executed verification
Actual behavior
Failed to perform verification
Reason analyze (If you can)
After reading the source code, I found that the type attribute in YamProxyConfiguration is Cluster when starting, but when creating ContextManager, the type attribute in the modeConfiguration parameter in the ContextManagerBuilderParameter is Standalone, indicating that I don't quite understand it
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Example codes for reproduce this issue (such as a github link).