[DOCS-3404] fsyncLock+auth clarification Created: 13/May/14 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: | Alexander Komyagin | Assignee: | Michael Paik |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
http://docs.mongodb.org/manual/reference/method/db.fsyncLock/ |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 27 weeks, 1 day ago | ||||
| Description |
|
On the fsyncLock doc page, we should warn users that fsyncLock may block reads, and hence it may block authentication attempts. So in systems with authentication enabled we recommend to keep the shell you used for fsyncLock() open. This way you will be able to reuse it for Unlock() later. Usually, users use fsyncLock/Unlock as part of their backup scripts. One way to have a single connection throughout the script is to use a scripting language that has a mongo driver (e.g. not bash but perl or python). |
| 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'}Signed-off-by: Sam Kleinman <samk@10gen.com> |