sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-03 01:18:10 +03:00
Code

ctdb:doc: Fix code spelling

Browse Source 
Best reviewed with: `git show --word-diff`.

Signed-off-by: Andreas Schneider <asn@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
This commit is contained in:
Andreas Schneider 2023-04-03 09:48:38 +02:00 committed by Andreas Schneider
parent e081fa4cc9
commit 409ede2d1f
3 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ctdb/doc/ctdb-tunables.7.xml
View File

@ -131,7 +131,7 @@ MonitorInterval=20
<title>DatabaseMaxDead</title>
<para>Default: 5</para>
<para>
Maximum number of dead records per hash chain for the tdb databses
Maximum number of dead records per hash chain for the tdb databases
managed by ctdb.
</para>
</refsect2>

4
ctdb/doc/ctdb.1.xml
View File

@ -321,7 +321,7 @@
This is the cluster node that is currently designated as the
leader. This node is responsible of monitoring the
consistency of the cluster and to perform the actual
recovery process when reqired.
recovery process when required.
</para>
<para>
Only one node at a time can be the designated leader. Which
@ -1127,7 +1127,7 @@ DB Statistics: locking.tdb
<para>
This command is used to administratively STOP a node in the cluster.
A STOPPED node is connected to the cluster but will not host any
public ip addresse, nor does it participate in the VNNMAP.
public ip addresses, nor does it participate in the VNNMAP.
The difference between a DISABLED node and a STOPPED node is that
a STOPPED node does not host any parts of the database which means
that a recovery is required to stop/continue nodes.

4
ctdb/doc/readonlyrecords.txt
View File

@ -121,7 +121,7 @@ very many readonly requests.
The ctdb_db structure is expanded so that it contains one extra TDB database for each
normal, non-persistent datbase.
normal, non-persistent database.
This new database is used for tracking delegations for the records.
A record in the normal database that has "HAVE_DELEGATION" set will always have a
corresponding record at the same key. This record contains the set of all nodes that
@ -334,7 +334,7 @@ Non-readonly enabled daemons fetching records from Readonly enabled daemons:
Non-readonly enabled daemons do not know, and never set the WANT_READONLY flag so these daemons will always request a full migration for a full fetch-lock for all records. Thus a request from a non-readonly enabled daemon will always cause any existing delegations to be immediately revoked. Access will work but performance may be harmed since there will be a lot of revoking of delegations.
Readonly enabled daemons fetching records with WANT_READONLY from non-readonly enabled daemons:
Non-readonly enabled daemons ingore the WANT_READONLY flag and never return delegations. They always return a full record migration.
Non-readonly enabled daemons ignore the WANT_READONLY flag and never return delegations. They always return a full record migration.
Full record migration is allowed by the protocol, even if the originator only requests the 'hint' WANT_READONLY,
so this access also interoperates between daemons with different capabilities.