[SERVER-17175] $isolated updates and deletes need X lock not IX Created: 04/Feb/15  Updated: 18/Sep/15  Resolved: 13/Feb/15

Status: Closed
Project: Core Server
Component/s: Concurrency, Write Ops
Affects Version/s: None
Fix Version/s: 3.0.0-rc9, 3.1.0

Type: Bug 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
Operating System: ALL
Backport Completed:
Participants:

 Comments   
Comment by Githook User [ 15/Feb/15 ]

Author:

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

Message: SERVER-17175 Use X lock for $isolated updates and deletes

(cherry picked from commit 7286fb36c36daaa8ee4941fa5f6c225b0a25dc61)
Branch: v3.0
https://github.com/mongodb/mongo/commit/e71db695221e39b3b6aa972d7503ca8c52c8fd55

Comment by Githook User [ 13/Feb/15 ]

Author:

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

Message: SERVER-17175 Use X lock for $isolated updates and deletes
Branch: master
https://github.com/mongodb/mongo/commit/7286fb36c36daaa8ee4941fa5f6c225b0a25dc61

Comment by Mathias Stearn [ 04/Feb/15 ]

scotthernandez For MMAPv1 and any other non-doc-locking engine, all IX locks on collections are already promoted to X so this would have no effect on them.

Comment by Scott Hernandez (Inactive) [ 04/Feb/15 ]

I'm not sure this is need for mmapv1 since the yielding policy doesn't allow yielding once a document is written, and it already takes the collection lock. For docLevelLocking this does seem like an issue that needs to be addressed.

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