[SERVER-23976] repairDatabase command on a new, different-cased database terminates server Created: 28/Apr/16 Updated: 03/Jan/18 Resolved: 21/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.3.3 |
| Fix Version/s: | 3.5.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | Storage 2016-11-21, Storage 2016-12-12 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
In versions prior to 3.3.3, running repairDatabase on a new, different-cased database returns this error:
In 3.3.3+, the same command terminates the server:
|
| Comments |
| Comment by Githook User [ 21/Nov/16 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: |
| Comment by Githook User [ 18/Nov/16 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: Revert " This reverts commit 512f655b5b4d3fd713a035633b6e857e85db8e7b. |
| Comment by Githook User [ 18/Nov/16 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: |
| Comment by Max Hirschhorn [ 04/Nov/16 ] |
|
Re-opening because the commit was reverted. |
| Comment by Githook User [ 04/Nov/16 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@mongodb.com'}Message: Revert " This reverts commit 69373e54608616c99905d5135bfd635367606ad2. Conflicts: |
| Comment by Githook User [ 03/Nov/16 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |
| Comment by Githook User [ 03/Nov/16 ] |
|
Author: {u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}Message: |
| Comment by Githook User [ 03/Nov/16 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: |
| Comment by Eric Milkie [ 25/Oct/16 ] |
|
The issue is that the repair database command doesn't check to see if the database exists first, before repairing. This amusingly results in different behavior on WiredTiger versus mmap, if you give it a database that doesn't exist (and also doesn't conflict in case with other existing databases). |