[DOCS-1638] fsyncLock/Unlock pages should warn about nested calls to fsyncLock Created: 25/Jun/13  Updated: 30/Oct/23  Resolved: 01/Jul/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Thomas Rueckstiess Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates DOCS-1603 Warn that fsyncLock() may prevent bei... Closed
Participants:
Days since reply: 10 years, 34 weeks, 1 day ago

 Description   

Calling fsyncLock multiple times without calling fsyncUnlock in between can cause a race condition and block a node until the process is restarted, see SERVER-6302.

Until the bug is fixed, users should be warned in the documentation for fsyncLock and fsyncUnlock that this can happen and advise against calling fsyncLock repeatedly. A work-around (inspecting if a node is locked before locking) is given on the server ticket.

A common use case is to run automated backup scripts repeatedly (e.g. cron jobs). If the backup doesn't finish before the next one is scheduled, these kinds of nested calls can happen.


Generated at Thu Feb 08 07:41:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.