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

Require OperationContext for egress commands

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Service Arch
    • Fully Compatible

      We have the option to provide an OperationContext with a RemoteCommandRequest here. However, we do not require that OperationContext pointer be valid. We should start making progress towards requiring that OperationContext. If we do so, we can make use of operation deadlines and better trace the state of remote operations.

      Evaluating places where RemoteCommandRequest is used, they tend to lack an explicit OperationContext. However, I'm nearly certain most possess a Client on thread. This ticket may involve investigation and submitting child tickets to other teams.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: