From 89bf1d2e34c7f4afe8c75dd5cf48e8564104f71b Mon Sep 17 00:00:00 2001 From: Amitay Isaacs Date: Mon, 7 Apr 2014 12:00:54 +1000 Subject: ctdb-doc: Remove commands that have been deleted Signed-off-by: Amitay Isaacs Reviewed-by: Martin Schwenke --- ctdb/doc/ctdb.1.xml | 64 ----------------------------------------------------- 1 file changed, 64 deletions(-) diff --git a/ctdb/doc/ctdb.1.xml b/ctdb/doc/ctdb.1.xml index 5d00961133..95a67dbeed 100644 --- a/ctdb/doc/ctdb.1.xml +++ b/ctdb/doc/ctdb.1.xml @@ -1673,70 +1673,6 @@ Server id 0:14765 exists - - vacuum [<parameter>max-records</parameter>] - - Over time CTDB databases will fill up with empty deleted - records which will lead to a progressive slow down of CTDB - database access. This command is used to prune all databases - and delete all empty records from the cluster. - - - - By default, vacuum will delete all empty records from all databases. - If [max_records] is specified, the command will only delete the first - [max_records] empty records for each database. - - - - Vacuum only deletes records where the local node is the - lmaster. To delete all records from the entire cluster you - need to run a vacuum from each node. - - This command is not disruptive. Samba is unaffected and will still be able to read/write records normally while the database is being vacuumed. - - - - Example: ctdb vacuum - - - - By default, this operation is issued from the 00.ctdb event script every 5 minutes. - - - - - repack [max_freelist] - - Over time, when records are created and deleted in a TDB, the TDB list of free space will become fragmented. This can lead to a slowdown in accessing TDB records. - This command is used to defragment a TDB database and pruning the freelist. - - - - If [max_freelist] is specified, then a database will only be repacked if it has more than this number of entries in the freelist. - - - During repacking of the database, the entire TDB database will be locked to prevent writes. If samba tries to write to a record in the database during a repack operation, samba will block until the repacking has completed. - - - - This command can be disruptive and can cause samba to block for the duration of the repack operation. In general, a repack operation will take less than one second to complete. - - - - A repack operation will only defragment the local TDB copy of the CTDB database. You need to run this command on all of the nodes to repack a CTDB database completely. - - - - Example: ctdb repack 1000 - - - - By default, this operation is issued from the 00.ctdb event script every 5 minutes. - - - -