This issue might have the following causes:
- The database’s primary keys are not evenly distributed (for example, when you enable
SHARD_ROW_ID_BITS
). - The upstream database is TiDB and the exported table is a partitioned table.
For the above cases, Dumpling splits excessively large data chunk for the export and sends queries with excessively large results. To address the issue, you can contact us to get the nightly version of Dumpling.