kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From danburk...@apache.org
Subject kudu git commit: [docs] Revise disk-failure-recovery workflow
Date Wed, 19 Apr 2017 18:00:39 GMT
Repository: kudu
Updated Branches:
  refs/heads/branch-1.3.x 3211d9781 -> 73918d055


[docs] Revise disk-failure-recovery workflow

Missed a few comments in the original commit.

Change-Id: I35c2ca56fdcf07917e7e0ba7f0d9be7b6bb19568
Reviewed-on: http://gerrit.cloudera.org:8080/6608
Reviewed-by: Todd Lipcon <todd@apache.org>
Tested-by: Kudu Jenkins
(cherry picked from commit 4649cd8af9c1fb3867639fa75d89ac1bddd35f66)
Reviewed-on: http://gerrit.cloudera.org:8080/6688


Project: http://git-wip-us.apache.org/repos/asf/kudu/repo
Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/73918d05
Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/73918d05
Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/73918d05

Branch: refs/heads/branch-1.3.x
Commit: 73918d05558d87739447f5322c69ac65424806e7
Parents: 3211d97
Author: Dan Burkert <danburkert@apache.org>
Authored: Tue Apr 11 14:32:16 2017 -0700
Committer: Dan Burkert <danburkert@apache.org>
Committed: Wed Apr 19 17:59:56 2017 +0000

----------------------------------------------------------------------
 docs/administration.adoc | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kudu/blob/73918d05/docs/administration.adoc
----------------------------------------------------------------------
diff --git a/docs/administration.adoc b/docs/administration.adoc
index 813d097..f3fad35 100644
--- a/docs/administration.adoc
+++ b/docs/administration.adoc
@@ -590,7 +590,7 @@ $ kudu cluster ksck --checksum_scan --tables IntegrationTestBigLinkedList
master
 === Recovering from Disk Failure
 
 // TODO(dan): revise this once KUDU-616 is fixed.
-Kudu tablet servers are not resistent to disk failure. When a disk containing a
+Kudu tablet servers are not resilient to disk failure. When a disk containing a
 data directory or the write-ahead log (WAL) dies, the entire tablet server must
 be rebuilt. Kudu will automatically re-replicate tablets on other servers after
 a tablet server fails, but manual intervention is needed in order to restore the
@@ -598,18 +598,18 @@ failed tablet server to a running state.
 
 The first step to restoring a tablet server after a disk failure is to replace
 the failed disk, or remove the failed disk from the data-directory and/or WAL
-configuration. Next, the existing data directories and WAL directory must be
-removed. For example, if the tablet server is configured with
+configuration. Next, the contents of the data directories and WAL directory must
+be removed. For example, if the tablet server is configured with
 `--fs_wal_dir=/data/0/kudu-tserver-wal` and
 `--fs_data_dirs=/data/1/kudu-tserver,/data/2/kudu-tserver`, the following
-commands will remove the existing data directories and WAL directory:
+commands will remove the data directories and WAL directory contents:
 
 [source,bash]
 ----
-$ rm -rf /data/0/kudu-tserver-wal /data/1/kudu-tserver /data/2/kudu-tserver
+$ rm -rf /data/0/kudu-tserver-wal/* /data/1/kudu-tserver/* /data/2/kudu-tserver/*
 ----
 
-After the WAL and data directories are removed, the tablet server process can be
+After the WAL and data directories are emptied, the tablet server process can be
 started. When Kudu is installed using system packages, `service` is typically
 used:
 


Mime
View raw message