[SERVER-6578] Can still make mongod hang fsyncLock and authentication Created: 24/Jul/12  Updated: 15/Aug/12  Resolved: 26/Jul/12

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Eliot Horowitz (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

Steps to reproduce (I've checked with 2.1.2 and the current master, ee1387026cb918a7b9b5dda47a791ea4e3643a41:

  1. Start up a mongod with --keyFile (does not need to be a replica set)
  2. Connect to that mongod via the shell

backup_test:PRIMARY> use admin
switched to db admin
backup_test:PRIMARY> db.addUser('dan', 'g')
{
	"user" : "dan",
	"readOnly" : false,
	"pwd" : "7c60b83b8e775def86996df8faf90335",
	"_id" : ObjectId("500eed6649494f669058a47e")
}
could not find getLastError object : "getlasterror failed: { \"errmsg\" : \"need to login\", \"ok\" : 0 }"
Tue Jul 24 14:45:59 uncaught exception: getlasterror failed: { "errmsg" : "need to login", "ok" : 0 }
> db.auth('dan', 'g')
1
backup_test:PRIMARY> db.fsyncLock()
{
	"info" : "now locked against writes, use db.fsyncUnlock() to unlock",
	"seeAlso" : "http://www.mongodb.org/display/DOCS/fsync+Command",
	"ok" : 1
}
backup_test:PRIMARY> db.addUser('foo', 'bar')
{
	"user" : "foo",
	"readOnly" : false,
	"pwd" : "3563025c1e89c7ad43fb63fcbcf1c3c6",
	"_id" : ObjectId("500eed7a49494f669058a47f")
}
^C^C
 
^C
 
^C^C^C
^C^C

Mongod cannot be interrupted (waits to finish the current command) and new connections to mongod can not be made.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 26/Jul/12 ]

Yes - still not fully fixed. See SERVER-1423

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