Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-82838

ReshardingOplogApplier uses {w: "majority", wtimeout: 60000} write concern when persisting resharding oplog application progress

    • Cluster Scalability
    • Fully Compatible
    • ALL
    • v7.2, v7.0, v6.0, v5.0
    • Cluster Scalability 2023-12-25
    • 2

      The PersistentTaskStore class called by the ReshardingOplogApplier uses WriteConcerns::kMajorityWriteConcernShardingTimeout when no argument is provided. The {w: "majority", wtimeout: 60000} write concern can lead resharding to fail with an operation-fatal error due to the write concern not being satisfied quickly enough. Furthermore, there is no requirement for the ReshardingOplogApplier to have its current batch become majority-committed before moving on to process the subsequent batch. This is because the new primary of the recipient shard will resume resharding batch application from wherever its local state left off from.

      The ReshardingOplogApplier should instead use {w: 1} for its write concern (for example).

            wenqin.ye@mongodb.com Wenqin Ye
            max.hirschhorn@mongodb.com Max Hirschhorn
            0 Vote for this issue
            5 Start watching this issue