[SERVER-2281] after a {fsync: 1, lock: 1}, "show dbs" hangs Created: 22/Dec/10  Updated: 21/Mar/13  Resolved: 22/Dec/10

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 1.6.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Alvin Richards (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-1423 reads often aren't possible while in ... Closed
Operating System: ALL
Participants:

 Description   

Problem:

After an

{fsync: 1, lock: 1}

a "show dbs" in another connections hangs with

> db.currentOp()
{
"inprog" : [
{
"opid" : 205,
"active" : true,
"lockType" : "write",
"waitingForLock" : true,
"secs_running" : 6991,
"op" : "query",
"ns" : "admin",
"query" :

{ "listDatabases" : 1 }

,
"client" : "127.0.0.1:55521",
"desc" : "conn"
}
],
"fsyncLock" : 1,
"info" : "use db.$cmd.sys.unlock.findOne() to terminate the fsync write/snapshot lock"
}

This block a mongodump, since this appears to execute the listDatabases command.

Reproduce:
1. shell 1 - execute

{fsync: 1, lock: 1}

2. shell 2 - execute "show dbs" ... command does not return

Business Case:

  • Usability
    Need to ensure that a mongodump will execute after an {fsync: 1, lock: 1}

    and it does issue any blocking calls.


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