Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-85275 Resharding oplog application should ignore DuplicateKey error
  3. SERVER-93223

Improve performance of collmod/ use separate approach to meet critical section requirements

XMLWordPrintableJSON

    • Type: Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Cluster Scalability 2024-07-08, Cluster Scalability 2024-07-22, Cluster Scalability 2024-08-19, Cluster Scalability 2024-09-02

      Currently, the code gated by the ReshardingSpuriousDuplicateKeyErrors feature flag solves the problem of spurious duplicate key errors by implementing subtasks 1, 2, and 3 of this ticket. The current problem is that the collmod operation is too slow and will cause the critical section to exceed the 2 second limit. There are several possible solutions to this problem that are discussed in the comments

            Assignee:
            Unassigned Unassigned
            Reporter:
            grant.xiao@mongodb.com Grant Xiao (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: