[DOCS-4194] Warning on the fsyncLock / Unlock steps in the backup page Created: 15/Oct/14  Updated: 16/Mar/15  Resolved: 20/Oct/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.13

Type: Improvement Priority: Major - P3
Reporter: Anil Kumar Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 9 years, 17 weeks, 2 days ago

 Description   

Page: http://docs.mongodb.org/manual/tutorial/backup-with-filesystem-snapshots/#create-backups-on-instances-that-do-not-have-journaling-enabled

This page should contain a warning message highlighting following two facts:

  • The fsyncLock / fsyncUnlock should happen on the same connection for safety else is susceptible to locking out the mongod instance that may need restart
  • An termination of connection once fsyncLock has been done, does not imply automatic fsyncUnlock and can lead to a locked out mongod instance. The application performing fsyncLock over a specific connection should ideally handle any error condition and perform an fsyncUnlock appropriately.


 Comments   
Comment by Githook User [ 20/Oct/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4194: clarify fsyncLock/fsyncUnlock use
Branch: master
https://github.com/mongodb/docs/commit/5b34fc2782d1e1a7be39370fdcea88fa14aa1de3

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