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

Default --enableMajorityReadConcern to true

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Storage Execution

      The SnapshotThread poses somewhat of a pathological use case for WiredTiger as it repeatedly seeks to the highest key in the oplog in the presence of concurrent inserts to the end of the tree. This operation is inherently unscalable as the seeking to the end of the RecordStore is not wait-free in the presence of concurrent inserts.

      We should run our full test suite with the SnapshotThread enabled to find any additional longevity/stability issues.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            adam.midvidy Adam Midvidy
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: