You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Lightning to import data, if pre-split is performed on the table and node rate limiting is enabled on TiKV, it cause continuous range regions to be distributed on the same store. This results in store-level hotspots during the import process, causing the import speed to fall far short of expectations. Currently, PD only determines balance and scatter regions based on the number of regions per store. Therefore, even if Lightning calls scatter regions before data import, it does not have the desired effect.
The text was updated successfully, but these errors were encountered:
Enhancement
When using Lightning to import data, if pre-split is performed on the table and node rate limiting is enabled on TiKV, it cause continuous range regions to be distributed on the same store. This results in store-level hotspots during the import process, causing the import speed to fall far short of expectations. Currently, PD only determines balance and scatter regions based on the number of regions per store. Therefore, even if Lightning calls scatter regions before data import, it does not have the desired effect.
The text was updated successfully, but these errors were encountered: