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

Handle differing ReadWriteConcernDefault behavior between roles

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Workload Scheduling
    • Workload Scheduling 2024-09-02, Workload Scheduling 2024-09-16, Workload Scheduling 2024-09-30, Workload Scheduling 2024-10-14

      On mongos/in the router role, ReadWriteConcernDefaults are obtained by doing a read from the config server; on configservers, a local read is done (nothing is done on shard servers). We need to ensure that the "getRWCDefaults" behavior in the router-role is the same with embedded routers as it is on dedicated mongos.

            Assignee:
            Unassigned Unassigned
            Reporter:
            george.wangensteen@mongodb.com George Wangensteen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: