TherChenYang commented on issue #31242: URL: https://github.com/apache/shardingsphere/issues/31242#issuecomment-2121560176
@ttfont Are you using the ShardingSphere-JDBC or ShardingSphere-Proxy? If it is the JDBC module, ShardingSphere is not responsible for data migration. You need to use a data migration tool to complete the migration of your 16 shards to 32 shards. During the migration process, for both old and new clusters, you need to perform dual write operations by reading data from the old cluster (16 shards). Once the overall migration process is completed, change ShardingSphere's configuration so that both read and write operations are routed to the new cluster. -- 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]
