[DOCS-1603] Warn that fsyncLock() may prevent being able to log into shell to fsyncUnlock() Created: 13/Jun/13  Updated: 16/Mar/15  Resolved: 15/Aug/14

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

Type: Improvement Priority: Major - P3
Reporter: Andre de Frere Assignee: Michael Paik
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-1364 Documentation doesn't indicate that d... Closed
is duplicated by DOCS-3681 warn users that fsyncUnlock needs to ... Closed
is duplicated by DOCS-1638 fsyncLock/Unlock pages should warn ab... Closed
Related
related to SERVER-1423 reads often aren't possible while in ... Closed
Participants:
Days since reply: 9 years, 27 weeks, 1 day ago

 Description   

As per SERVER-1423, it is possible to fsyncLock() and close the shell, but then not be able to reconnect to the shell in order to fsyncUnlock(). In the docs page for 'fsync' there is a warning that reads may not be possible. It may be necessary to have a more explicit warning that reconnecting to the shell may also not be possible, until SERVER-1423 and surrounding issues are resolved.



 Comments   
Comment by Githook User [ 12/Aug/14 ]

Author:

{u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}

Message: DOCS-1603, DOCS-3404

Signed-off-by: Sam Kleinman <samk@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/ef6f5771d072000b373bc874b42d84ff605eb736

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