[SERVER-16677] mongod.lock file should be present in data directory regardless of storage engine selected Created: 28/Dec/14 Updated: 10/Feb/15 Resolved: 05/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.8.0-rc4 |
| Fix Version/s: | 2.8.0-rc5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa, wiredtiger | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | Linux | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
Currently, mongod.lock is created in the data directory by the mmapv1 initialization code and is not present when another storage engine (eg. WiredTiger) is selected. We should always ensure that this file is created (and locked) regardless of the storage engine used. ----------
Version: b0014456dd |
| Comments |
| Comment by Githook User [ 09/Jan/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 05/Jan/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 05/Jan/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 05/Jan/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |