[DOCS-9265] 3.4: Clarify multiple fsyncLock behavior Created: 02/Nov/16 Updated: 26/Jul/18 Resolved: 29/Mar/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | James Wahlin | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 5 years, 45 weeks, 6 days ago | ||||||||||||||||
| Story Points: | 1 | ||||||||||||||||
| Description |
Documentation Changes
DescriptionCurrently (and historically) users could call fsyncLock multiple times which would then require the same number of fsyncUnlock calls to unlock the mongod instance. We should make this behavior clear in both our fsyncLock and fsyncUnlock documentation. I would recommend changing just for 3.4 as there exists a race condition that makes multiple lock/unlock unsafe prior to 3.4 (see Additionally, with the fix for |
| Comments |
| Comment by Githook User [ 29/Mar/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 29/Mar/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |
| Comment by James Wahlin [ 22/Nov/16 ] |
|
andrew.aldridge - looks like |
| Comment by Allison Reinheimer Moore [ 07/Nov/16 ] |
|
To you for grooming, andrew.aldridge |