Use all threads for secondary applyOps

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.14
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2016-09-19
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As part of SERVER-24242 we schedule the writes to the oplog in the same thread pool as application. To avoid a perverse case, if only one thread is used for oplog writing, we use one less for application. As of SERVER-7200, we wait for oplog writes to complete before starting application. Therefore it no longer makes sense to reduce the threads available to application.

            Assignee:
            Mathias Stearn
            Reporter:
            Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: