Make internal command write concern timeout on sharded clusters configurable

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      (Split from SERVER-84356).

      The current value of kWriteConcernTimeoutSharding is hardcoded at 60 seconds. In some cases, it might be desirable to modify it so we should consider making it configurable.

            Assignee:
            Unassigned
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: