[JAVA-1719] Re-implement Mongo.unlock and Mongo.isLocked with new database commands Created: 25/Mar/15  Updated: 27/May/22  Resolved: 06/Oct/15

Status: Closed
Project: Java Driver
Component/s: Command Operations
Affects Version/s: None
Fix Version/s: 3.2.0

Type: New Feature Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Jeffrey Yemin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-7775 Make special commands (inprog, killop... Closed
is depended on by DRIVERS-213 Make special commands (inprog, killop... Closed
Epic Link: MongoDB 3.2
Server Compat: 3.1

 Description   

The Mongo.unlock method currently queries the "$cmd.sys.unlock" method to unlock the server. The 3.2 server will support an fsyncUnlock command to replace this. The driver should call that command if it detects a 3.2 server. Otherwise it should ball back to the existing way of doing it.

Similarly, the Mongo.isLocked method queries the "$cmd.sys.inprog" collection. The 3.2 server will support a currentOp command that does the same thing. The driver should call that command if it detects a 3.2 server. Otherwise it should ball back to the existing way of doing it.



 Comments   
Comment by Jeffrey Yemin [ 07/Dec/15 ]

The 3.2.0 driver, which contains a fix for this issue, has been released today.

Comment by Githook User [ 06/Oct/15 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: JAVA-1948, JAVA-1719: Support query-related commands introduced in MongoDB 3.2
Support the find, getMore and explain commands
Support the currentOp and fsyncUnlock commands
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/7253aa585ce95c350d9f510a9ff994af6119e0ab

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