Download & Extend
Mongodb » Issues

Create locking framework implementation

Posted by crea on June 6, 2011 at 1:38pm
Project:Mongodb
Version:6.x-1.x-dev
Component:Locking
Category:task
Priority:normal
Assigned:Unassigned
Status:needs review

Issue Summary

Need support for locking framework

Login or register to post comments

Comments

#1

Posted by crea on June 6, 2011 at 1:40pm
Component:Miscellaneous» Locking

#2

Posted by crea on June 13, 2011 at 1:20am
Version:7.x-1.x-dev» 6.x-1.x-dev
Status:active» needs review

First version for D6.

AttachmentSizeStatusTest resultOperations
mongodb_lock_1180056.patch9.11 KBTest request sentNoneView details

#3

Posted by crea on June 13, 2011 at 9:56pm

We could also use MongoId($name) as an _id

#4

Posted by crea on June 23, 2011 at 7:57am

Need progressing lock_wait() like in the Memcache module

#5

Posted by crea on June 26, 2011 at 5:12am
Title:Implement lock.inc (D6 & D7)» Create locking framework implementation

#6

Posted by crea on June 26, 2011 at 5:13am
Status:needs review» needs work

#7

Posted by crea on June 26, 2011 at 7:19am
Status:needs work» needs review

Updated patch. Added variable collection names. Borrowed progressive lock_wait() implementation from Memcache project and also included configurable sleep intervals.

AttachmentSizeStatusTest resultOperations
mongodb_lock_1180056_7.patch10.84 KBTest request sentNoneView details

#8

Posted by crea on July 18, 2011 at 8:51pm
Status:needs review» needs work

Looks like using safe updates was not good idea because MongoDB syncs that to disk...But can we use it without safe option at all ? We need to be sure about the lock.

#9

Posted by crea on August 3, 2011 at 5:24pm

I wasn't paying attention. There's a separate fsync option

"fsync"

Boolean, defaults to FALSE. Forces the insert to be synced to disk before returning success. If TRUE, a safe insert is implied and will override setting safe to FALSE.

#10

Posted by crea on August 3, 2011 at 5:25pm
Status:needs work» needs review