[SERVER-3609] write starvation can make secondaries fall behind when under heavy load Created: 16/Aug/11  Updated: 11/Jul/16  Resolved: 14/Oct/11

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

Type: Improvement Priority: Major - P3
Reporter: Dwight Merriman Assignee: Dwight Merriman
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

we acquire a write lock on every operation applied. if we do multiple operations in a write lock starvation can be avoided when there is very heavy simultaneous read load.



 Comments   
Comment by auto [ 14/Oct/11 ]

Author:

{u'login': u'dwight', u'name': u'Dwight', u'email': u'dwight@10gen.com'}

Message: SERVER-3609 we acquire a write lock on every operation applied. if we do multiple operations in a write lock starvation can be avoided when there is very heavy simultaneous read load.
Branch: master
https://github.com/mongodb/mongo/commit/9a02f4a03fa11e0f1eab4b8169b94f4a0615923c

Generated at Thu Feb 08 03:03:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.