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

Profiling transaction operations should always succeed

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying, Replication
    • Labels:
      None
    • Replication

      Currently its possible for an operation in a transaction to complete successfully, but no profiling entry for that operation to be written, even if the op should have been profiled based on the duration of the op and the current profiler configuration. The profile entry can fail to be written if there's any contention grabbing the lock on the system.profile collection, or if the operation gets killed after it has completed but before it has been profiled.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: