Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13345

Investigate changes in SERVER-45098: Test application of RWCDefaults to all commands

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: 4.3.3
    • Component/s: manual
    • Labels:

      Description

      Description

      Downstream Change Summary

      Normally, the default writeConcern will be applied to all incoming operations that accept WC, including admin commands. However, there is a subset of admin commands referred to as "sharding admin commands", which are different because they perform operations on the config server primary with w:majority (they can be found by grepping for calls to appendMajorityWriteConcern).

      The current behaviour for sharding admin commands is:

      • supplied WC { w: X, wtimeout: Y }: apply { w: "majority", wtimeout: Y }
      • no supplied WC: apply { w: "majority", wtimeout: 60000 }

      This ticket has not changed this behaviour.

      However, the behaviour for these commands in the presence of default writeConcern has a subtle adjustment. If the default WC includes wtimeout less than 60000, then for sharding admin commands only the applied WC will have its wtimeout upgraded to 60000. To put this another way, for sharding admin commands the minimum wtimeout from default writeConcern is 60000. Spelling this out into the different cases:

      • supplied WC { w: X, wtimeout: Y }: apply { w: "majority", wtimeout: Y }
      • no supplied WC and no default WC: apply { w: "majority", wtimeout: 60000 }
      • no supplied WC and default WC { w: X, wtimeout: Y }: apply { w: "majority", wtimeout: max(60000, Y) }, ie:
        • for Y <= 60000: apply { w: "majority", wtimeout: 60000 }
        • for Y > 60000: apply { w: "majority", wtimeout: Y }

      Again, this is all only for sharding admin commands, and other commands/ops are not subject to this behaviour.

      Description of Linked Ticket

      null

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Ravind Kumar Ravind Kumar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 34 weeks, 1 day ago
                Date of 1st Reply: