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

DBDirectClient shouldn't unexpectedly modify opCtx

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Storage Execution
    • 5

    Description

      As part of SERVER-53935 we realized that DBDirectClient was unexpectedly modifying the readConcernArgs in the callers opCtx.

      This ticket is to consider using an AlternativeClientRegion in DBDirectClient so that there is no possibility that the callers opCtx is modified unexpectedly. Instead, callers will need to explicitly transfer any state they wish for a client to inherit (e.g. readConcern, maxTimeMs)

       

      Acceptance criteria:

      DBDirectClient doesn't unexpectedly modify opCtx. 

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: