diff options
| author | Volker Lendecke <vl@samba.org> | 2012-02-20 12:21:48 +0100 |
|---|---|---|
| committer | Michael Adam <obnox@samba.org> | 2012-02-21 10:52:57 +0100 |
| commit | 46244f0d5068b95e3eed6ffdaa2ca4eac9f5f15b (patch) | |
| tree | 120824cadac7f75f9123773fbbf978d40ea1a8d0 /ctdb/doc | |
| parent | 81fb334cff94207c8e7806dcf47b4ceadfeb30b7 (diff) | |
| download | samba-46244f0d5068b95e3eed6ffdaa2ca4eac9f5f15b.tar.gz samba-46244f0d5068b95e3eed6ffdaa2ca4eac9f5f15b.tar.xz samba-46244f0d5068b95e3eed6ffdaa2ca4eac9f5f15b.zip | |
Fix some documentation typos
Signed-off-by: Michael Adam <obnox@samba.org>
(This used to be ctdb commit 67516f2eaf0b8b0f6aa4ecb0f1c44af53b992fbb)
Diffstat (limited to 'ctdb/doc')
| -rw-r--r-- | ctdb/doc/readonlyrecords.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/ctdb/doc/readonlyrecords.txt b/ctdb/doc/readonlyrecords.txt index e09aa41dd0b..d108ffde36a 100644 --- a/ctdb/doc/readonlyrecords.txt +++ b/ctdb/doc/readonlyrecords.txt @@ -23,7 +23,7 @@ We can not make backward incompatible changes the ctdb_ltdb header for the recor A Read-Only lock enabled ctdb demon must be able to interoperate with a non-Read-Only lock enbled daemon. -Getting a Read-Only look should not be slower than getting a Read-Write lock. +Getting a Read-Only lock should not be slower than getting a Read-Write lock. When revoking Read-Only locks for a record, this should involve only those nodes that currently hold a Read-Only lock and should avoid broadcasting opportunistic revocations. @@ -102,7 +102,7 @@ requests. -Once the revoke process is completedtThere will be at least one deferred request to +Once the revoke process is completed there will be at least one deferred request to access this record. That is the initical call to for an exclusive fetch_lock() that triggered the revoke process to be started. In addition to this deferred request there may also be additional requests that have @@ -201,7 +201,7 @@ This will change to instead to something like finished: If the record does not yet exist in the local TDB, we always perform a full fetch for a -Read-Write lock even if only a Read-Only lock ws requested. +Read-Write lock even if only a Read-Only lock was requested. This means that for first access we always grab a Read-Write lock and thus upgrade any requests for Read-Only locks into a Read-Write request. This creates the record, migrates it onto the node and makes the local node become @@ -230,7 +230,7 @@ If this is the LMASTER for the record and the record does not yet exist, LMASTER return an error back to the client (*A above) and the client will try to recover. In particular, LMASTER will not create a new record for this case. -If this is the LMASTER for the record and the record exists, the PDU will be forwrded to +If this is the LMASTER for the record and the record exists, the PDU will be forwarded to the DMASTER for the record. If this node is not the DMASTER for this record, we forward the PDU back to the @@ -279,7 +279,7 @@ be no-op (*B below)) Recovery process changes ======================== -A recovery implicitely clears/revokes any read only records and delegations from all +A recovery implicitly clears/revokes any read only records and delegations from all databases. During delegations of Read-Only locks, this is done in such way that delegated records |