[SERVER-620] mongod thinks a background process is running for a db, even when it's not Created: 09/Feb/10  Updated: 12/Jul/16  Resolved: 10/Feb/10

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

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Dwight Merriman
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-606 unit tests for background indexing Closed
Participants:

 Description   

<http://buildbot.mongodb.org/builders/Linux%2064-bit%20Legacy/builds/162/steps/test/logs/stdio>

dbadmin.js claims it can't close all databases because a background operation is in progress, but the background index build from the earlier index11.js test has already finished.



 Comments   
Comment by auto [ 10/Feb/10 ]

Author:

{'login': 'dwight', 'name': 'Dwight', 'email': 'dmerriman@gmail.com'}

Message: SERVER-620
mongod thinks a background process is running for a db, even when it's not
http://github.com/mongodb/mongo/commit/635a16e94c583d7fc97ff65e32aa7f058caeefe0

Comment by auto [ 09/Feb/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-606 SERVER-620 disable test
http://github.com/mongodb/mongo/commit/2e5494cf788d9c736bd9ba7799c7439f2d0f956b

Comment by Aaron Staple [ 09/Feb/10 ]

After restarting mongod, dbadmin.js passes again.

Comment by Aaron Staple [ 09/Feb/10 ]

Pretty easy to reproduce - just run index11.js and then dbadmin.js. Even if I wait a while or run dbadmin.js several times, it always fails after index11.js.

Comment by Aaron Staple [ 09/Feb/10 ]

again
<http://buildbot.mongodb.org/builders/Linux%2064-bit%20Legacy/builds/164/steps/test/logs/stdio>

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