Investigate whether replay protection logic has to be added to _shardsvrConvertToCappedParticipant

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • None
    • 3
    • TBD
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      The command handler of _shardsvrConvertToCappedParticipant is expected to receive requests associated to checked-out sessions and with a majority write concern attached, but it does not include the usual "AlternativeClientRegion + noop write on the original operation context" logic to apply replay protection. 

              Assignee:
              Unassigned
              Reporter:
              Paolo Polato
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: