diff options
| author | sueloverso <sue@mongodb.com> | 2016-08-21 22:28:52 -0400 |
|---|---|---|
| committer | Alex Gorrod <alexander.gorrod@mongodb.com> | 2016-08-22 12:28:52 +1000 |
| commit | 46b2bd44376eb311eda470e422d54abfdeb93a87 (patch) | |
| tree | f2809a76f3a3be72dd60e9078bbe27f66b2029f1 | |
| parent | 36c2663b813216f9e10052ceeb2516fca5586496 (diff) | |
| download | mongo-46b2bd44376eb311eda470e422d54abfdeb93a87.tar.gz | |
WT-2795 Update documentation about read-only mode (#2970)
Explicitly state that parallel readonly handles depend on WT home directory not having write permission.
| -rw-r--r-- | src/docs/readonly.dox | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/docs/readonly.dox b/src/docs/readonly.dox index ad4a94a73f1..35378cf9567 100644 --- a/src/docs/readonly.dox +++ b/src/docs/readonly.dox @@ -47,7 +47,8 @@ One unusual affect of read-only operations is the potential for multiple read-only database handles open on the same database at the same time. WiredTiger prevents multiple connection handles by writing a lock file, and this locking is done even in read-only mode. However, if the lock -file cannot be written, opening in read-only mode is still allowed to +file cannot be written, that is, if the WiredTiger home directory does not +have write permission, opening in read-only mode is still allowed to proceed. For that reason, multiple read-only connection handles could be open at the same time. Normal locking occurs if the lock file can be written in read-only mode, preventing multiple database connections. |