[SERVER-16259] rocks storage engine needs to support document locking Created: 21/Nov/14  Updated: 28/Apr/15  Resolved: 04/Dec/14

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 2.8.0-rc2

Type: Bug Priority: Major - P3
Reporter: Siying Dong Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-16604 Improve integration with rocks Closed
Related
related to SERVER-16309 Fix rocks_recovery_unit Closed
is related to SERVER-1241 Document-level locking Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

RocksDB storage engine now doesn't fully support document locking. It cannot deal with recovery unit conflicts, causing uniqueness not guaranteed in unique index, and possible document update loss.

This JIRA is to have a short term fix for it.



 Comments   
Comment by Githook User [ 02/Dec/14 ]

Author:

{u'username': u'igorcanadi', u'name': u'Igor Canadi', u'email': u'icanadi@fb.com'}

Message: SERVER-16259 Rocks storage engine needs to support document locking

SERVER-16309 - Fix rocks_recovery_unit

SERVER-15744 Concurrency fix – Fixed jstests/core/bench_test3.js

Signed-off-by: Matt Kangas <matt.kangas@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/efb33fd38bd0e8733d14f657e7fa634880ec8f1d

Comment by Siying Dong [ 21/Nov/14 ]

The patch is in is in branch rocks_doc_locking of fork mongodb-partners: https://github.com/mongodb-partners/mongo/commits/rocks_doc_locking ready to merge.

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