[SERVER-10184] file allocation race when database is dropped immediately Created: 11/Jul/13 Updated: 01/Apr/15 Resolved: 06/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Mathias Stearn |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
Came up in a test case here: From Matt: Jul 09 08:12 6bc6dc7360b9... failure #1482 Failed test_12 http://buildbot.mongodb.org/builders/Nightly%20Linux%2064-bit/builds/1482
Seems like the file allocator is still working on the database after it's dropped? |
| Comments |
| Comment by auto [ 07/Oct/13 ] | ||||||||||||||
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Extra debugging for jstests/dropdb.js Failure case: | ||||||||||||||
| Comment by Matt Kangas [ 07/Oct/13 ] | ||||||||||||||
|
Hit again on V2.4 Windows 64-bit: http://buildbot.mongodb.org:8081/builders/V2.4%20Windows%2064-bit/builds/207 | ||||||||||||||
| Comment by Daniel Pasette (Inactive) [ 01/Sep/13 ] | ||||||||||||||
|
Hit again on Linux 64 v2.4: http://buildbot.mongodb.org:8081/builders/V2.4%20Linux%2064-bit/builds/197 | ||||||||||||||
| Comment by Matt Kangas [ 06/Aug/13 ] | ||||||||||||||
|
Happened again, this time on V2.4. Sadly your extra debugging info hasn't been backported. V2.4 Linux RHEL 64-bit Build #154 (Mon Aug 5, rev 3fc69c4aa) http://buildlogs.mongodb.org/V2.4%20Linux%20RHEL%2064-bit/builds/154/test/parallel/basic.js
| ||||||||||||||
| Comment by auto [ 11/Jul/13 ] | ||||||||||||||
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Extra debugging for jstests/dropdb.js Failure case: | ||||||||||||||
| Comment by Mathias Stearn [ 11/Jul/13 ] | ||||||||||||||
|
The theory that the file was created after the db was dropped seems incorrect both based on examination of the code and the long lines. The drop waits for the all pending files to be created before deleting, as seen in the order of the following log lines (intermediate lines removed for clarity):
I'll add some debugging info to the test to make it easier to debug if it fails again. | ||||||||||||||
| Comment by Greg Studer [ 11/Jul/13 ] | ||||||||||||||
|
Initially seen in this ticket, but unrelated to the top-level issue there. |