[SERVER-26011] Use all threads for secondary applyOps Created: 07/Sep/16  Updated: 19/Nov/16  Resolved: 08/Sep/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.3.14

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2016-09-19
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 08/Sep/16 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-26011 Use all threads for secondary application
Branch: master
https://github.com/mongodb/mongo/commit/1083942cef731e876b8c7ee029057a9fcd252336

Generated at Thu Feb 08 04:10:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.