[SERVER-71028] MigrationChunkClonerSourceLegacy::nextCloneBatch should ignore prepare conflict Created: 02/Nov/22  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam1, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-68361 LogTransactionOperationsForShardingHa... Closed
related to SERVER-40791 Chunk migration clone blocks behind p... Closed
related to SERVER-76546 _migrateClone can deadlock with prepa... Closed
Assigned Teams:
Cluster Scalability
Participants:

 Description   

MigrationChunkClonerSourceLegacy::nextCloneBatch should ignore prepare conflict when fetching documents.

Otherwise, they will end up unnecessarily waiting for prepare conflict to get resolved. It is okay for migration to ignore prepare conflicts because it already captures all ongoing modifications to documents in the chunk range that will end up getting committed.


Generated at Thu Feb 08 06:17:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.