Handle differing ReadWriteConcernDefault behavior between roles

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Workload Scheduling
    • Fully Compatible
    • Workload Scheduling 2024-09-02, Workload Scheduling 2024-09-16, Workload Scheduling 2024-09-30, Workload Scheduling 2024-10-14
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
            Reporter:
            George Wangensteen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: