[SERVER-21033] Sharding minOpTime info writes should not wait for read concern while holding a lock Created: 20/Oct/15  Updated: 27/Oct/15  Resolved: 21/Oct/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.2.0-rc1

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-19934 Ill-timed crash at end of chunk migra... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding B (10/30/15)
Participants:

 Description   

Waiting for write concern while holding a lock opens up opportunities for stalling replication heartbeats and for deadlocks involving the local database.



 Comments   
Comment by Githook User [ 21/Oct/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-21033 Do not wait for write concern under lock
Branch: master
https://github.com/mongodb/mongo/commit/f7f592e92b3146e20d311a35492116d7488e7e2b

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