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
Copy file name to clipboardExpand all lines: doc/command-line-flags.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,10 +110,10 @@ Controls how many rows `gh-ost` copies in each row-copy iteration. The default i
110
110
111
111
Parallel copy requires checkpoints because parallel INSERTs can go out of sequential order and leave gaps in target table. gh-ost checkpoints are consistent and do not have gaps, so resuming from a checkpoint will make the target table consistent again.
112
112
113
-
Consistency is ensured by using
114
-
-INSERT IGNORE/SELECT FOR SHARE for row copy (current gh-ost behavior)
115
-
-DELETE/INSERT by DML applier when unique key change is detected (current gh-ost behavior)
116
-
-advanceFrontier call to ensure that checkpoints have no gaps (used by parallel-copy only)
113
+
Consistency is ensured by using:
114
+
-`INSERT IGNORE`/`SELECT FOR SHARE` for row copy (current gh-ost behavior)
115
+
-`DELETE`/`INSERT` by DML applier when unique key change is detected (current gh-ost behavior)
116
+
-`advanceFrontier` call to ensure that checkpoints have no gaps (used by parallel-copy only)
117
117
Without all of those, consistency of parallel copy cannot be guaranteed (for example, row copy could insert row back after it was deleted). In existing serial mode, the problem is much easier because DML applier is never parallel with row copy.
migrationContext.Log.Warningf("--parallel-copy-workers=%d is high: throughput gains tend to plateau while load on the server grows. Consider <=%d.", migrationContext.ParallelCopyWorkers, base.RecommendedMaxCopyWorkers)
migrationContext.Log.Warningf("--parallel-copy-workers=%d is high: throughput gains tend to plateau while load on the server grows. Consider <=%d.", migrationContext.ParallelCopyWorkers, base.RecommendedMaxParallelCopyWorkers)
0 commit comments