pre-handle/generate snapshot CPU. Check the CPU usage of :-region-worker. If the curve is a straight line, the TiFlash node is stuck. Terminate the TiFlash process and restart it, or contact versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0

versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0 unit). For troubleshooting, refer to the previous sections of this document. If the corresponding curve of DML queue remain length is not 0 (usually the maximum is not more than 1024), it indicates that

versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0 unit). For troubleshooting, refer to the previous sections of this document. If the corresponding curve of DML queue remain length is not 0 (usually the maximum is not more than 1024), it indicates that

versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0 unit). For troubleshooting, refer to the previous sections of this document. If the corresponding curve of DML queue remain length is not 0 (usually the maximum is not more than 1024), it indicates that

versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0 unit). For troubleshooting, refer to the previous sections of this document. If the corresponding curve of DML queue remain length is not 0 (usually the maximum is not more than 1024), it indicates that

versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0 unit). For troubleshooting, refer to the previous sections of this document. If the corresponding curve of DML queue remain length is not 0 (usually the maximum is not more than 1024), it indicates that

versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0 unit). For troubleshooting, refer to the previous sections of this document. If the corresponding curve of DML queue remain length is not 0 (usually the maximum is not more than 1024), it indicates that

versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0 unit). For troubleshooting, refer to the previous sections of this document. If the corresponding curve of DML queue remain length is not 0 (usually the maximum is not more than 1024), it indicates that

versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0 unit). For troubleshooting, refer to the previous sections of this document. If the corresponding curve of DML queue remain length is not 0 (usually the maximum is not more than 1024), it indicates that

versions. • When there is no noticeable latency in the entire data migration link, the corresponding curve of DML queue remain length is almost always 0, and the maximum does not exceed the value of batch task configuration file. • If you find a noticeable latency in the data migration link, and the curve of DML queue �→ remain length corresponding to each q_* is almost the same and is almost always 0 unit). For troubleshooting, refer to the previous sections of this document. If the corresponding curve of DML queue remain length is not 0 (usually the maximum is not more than 1024), it indicates that