[SERVER-22352] In read only mode, don't fail startup if lockfile cannot be created due to a permission violation Created: 29/Jan/16 Updated: 22/Feb/16 Resolved: 16/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Adam Midvidy | Assignee: | Adam Midvidy |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Integration 10 (02/22/16) |
| Participants: |
| Description |
|
When MongoDB starts in read-only mode, it will still log an error and exit if a lock file exists. However, if lock file creation fails due to a permission violation (or other error generated from writing to a RO directory), startup will continue without an error. This work includes modifications to the lock file implementations on posix and windows as well as unit tests. |
| Comments |
| Comment by Githook User [ 17/Feb/16 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 17/Feb/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 17/Feb/16 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 16/Feb/16 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 05/Feb/16 ] |
|
Author: {u'username': u'ksuarz', u'name': u'Kyle Suarez', u'email': u'ksuarz@gmail.com'}Message: Revert " This reverts commit 77191d85a8a42d28cd32ce37365defae23556069. |
| Comment by Githook User [ 05/Feb/16 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: modify StorageEngineLockFile::open() to return a different status if it |