Need support for locking framework

Files: 
CommentFileSizeAuthor
#7 mongodb_lock_1180056_7.patch10.84 KBcrea
Test request sent.
[ View ]
#2 mongodb_lock_1180056.patch9.11 KBcrea
Test request sent.
[ View ]

Comments

crea’s picture

Component:Miscellaneous» Locking
crea’s picture

Version:7.x-1.x-dev» 6.x-1.x-dev
Status:Active» Needs review
StatusFileSize
new9.11 KB
Test request sent.
[ View ]

First version for D6.

crea’s picture

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

crea’s picture

Need progressing lock_wait() like in the Memcache module

crea’s picture

Title:Implement lock.inc (D6 & D7)» Create locking framework implementation
crea’s picture

Status:Needs review» Needs work
crea’s picture

Status:Needs work» Needs review
StatusFileSize
new10.84 KB
Test request sent.
[ View ]

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

crea’s picture

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.

crea’s picture

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.

crea’s picture

Status:Needs work» Needs review
fgm’s picture

Issue summary:View changes

Four years later and no committed version, can we agree to close this and say there will never be a stable 6.x version for lock ?

slashrsm’s picture

Status:Needs review» Closed (won't fix)

Agreed. If there is still anyone out there that needs this feel free to reopen and bring patch to RTBC state. Maintainers will be happy to commit it in that case.