[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: SERVER-22352 fix solaris
Branch: master
https://github.com/mongodb/mongo/commit/c666c99bef83a238f0853db3249f5a8543581b4f

Comment by Githook User [ 17/Feb/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-22352 fixed fassert code
Branch: master
https://github.com/mongodb/mongo/commit/935bafde6c4e7d28938d90c4ae91519246620ed0

Comment by Githook User [ 17/Feb/16 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-22352 do not fail startup if lockFile cannot be created in readOnly mode
Branch: master
https://github.com/mongodb/mongo/commit/6eb7010239c83e3d338d02175db6b82627e03964

Comment by Githook User [ 16/Feb/16 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-22352 lockFile changes for readOnly mode
Branch: master
https://github.com/mongodb/mongo/commit/1c7404095583a712d9e946e2751572c8973f13aa

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 "SERVER-22352 lockFile changes for readOnly"

This reverts commit 77191d85a8a42d28cd32ce37365defae23556069.
Branch: master
https://github.com/mongodb/mongo/commit/183a1d8af1d1d3d256732606609bfec49ae92dc4

Comment by Githook User [ 05/Feb/16 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-22352 lockFile changes for readOnly

modify StorageEngineLockFile::open() to return a different status if it
fails due to the dbpath having read-only permissions
Branch: master
https://github.com/mongodb/mongo/commit/77191d85a8a42d28cd32ce37365defae23556069

Generated at Thu Feb 08 04:00:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.