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

Database profiling should not serialize writes on all collections

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Storage
    • Labels:
      None

      Description

      Capped inserts on the primary are serialized because capped inserts on secondaries need to be serialized, and we need both primary and secondary to have the same level of write parallelism. Capped inserts on the secondary need to be serialized because we can only use the oplog to determine the ordering. This is a problem for a the system.profile collection which we use for Database profiling, since, in order to achieve the above, we use the metadata lock acquisition. This effectively produces database-level exclusive locking granularity for both reads and writes when the profiler is enabled.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-execution Backlog - Storage Execution Team
              Reporter:
              dmitry.agranat Dmitry Agranat
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated: