incubator-kudu git commit: Prefer 'replica' or 'host' to 'node' for accuracy

[jd...@apache.org]

Repository: incubator-kudu
Updated Branches:
  refs/heads/branch-0.7.0 313fc1603 -> c6554caac


Prefer 'replica' or 'host' to 'node' for accuracy

Change-Id: I849decc4c1e8690069af3bcf4d11240f81c1d987
Reviewed-on: http://gerrit.cloudera.org:8080/1957
Tested-by: Kudu Jenkins
Reviewed-by: Jean-Daniel Cryans
(cherry picked from commit 68a0aff59bc769656f7d10b0b7a93b6fcfac3edf)
Reviewed-on: http://gerrit.cloudera.org:8080/2046
Tested-by: Jean-Daniel Cryans


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

Branch: refs/heads/branch-0.7.0
Commit: c6554caacd94700be6aa291c48c6817381bb0e7f
Parents: 313fc16
Author: Misty Stanley-Jones <ms...@cloudera.com>
Authored: Fri Jan 29 10:16:47 2016 -0800
Committer: Jean-Daniel Cryans <jd...@gerrit.cloudera.org>
Committed: Thu Feb 4 21:03:57 2016 +0000

----------------------------------------------------------------------
 docs/administration.adoc        |  2 +-
 docs/introduction.adoc          | 11 +++++++----
 docs/release_notes.adoc         |  4 ++--
 docs/transaction_semantics.adoc |  2 +-
 4 files changed, 11 insertions(+), 8 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-kudu/blob/c6554caa/docs/administration.adoc
----------------------------------------------------------------------
diff --git a/docs/administration.adoc b/docs/administration.adoc
index d7f8271..f45d7f8 100644
--- a/docs/administration.adoc
+++ b/docs/administration.adoc
@@ -108,7 +108,7 @@ and label in the JSON output. This information is typically elided to save space
 bandwidth when fetching this page from a remote host.
 
 - `/metrics?include_raw_histograms=1` - include the raw buckets and values for histogram metrics,
-enabling accurate aggregation of percentile metrics over time and across nodes.
+enabling accurate aggregation of percentile metrics over time and across hosts.
 
 For example:
 

http://git-wip-us.apache.org/repos/asf/incubator-kudu/blob/c6554caa/docs/introduction.adoc
----------------------------------------------------------------------
diff --git a/docs/introduction.adoc b/docs/introduction.adoc
index 35f7b41..20a5b08 100644
--- a/docs/introduction.adoc
+++ b/docs/introduction.adoc
@@ -41,10 +41,13 @@ Kudu's design sets it apart. Some of Kudu's benefits include:
   requirements on a per-request basis, including the option for strict-serializable consistency.
 - Strong performance for running sequential and random workloads simultaneously.
 - Easy to administer and manage with Cloudera Manager.
-- High availability. Tablet Servers and Master use the <<raft>>, which ensures
-  availability even if _f_ nodes failing, given _2f+1_ nodes in the cluster.
-  Reads can be serviced by read-only follower tablets, even in the event of a
-  leader tablet failure.
+- High availability. Tablet Servers and Masters use the <<raft>>, which ensures that
+  as long as more than half the total number of replicas is available, the tablet is available for
+  reads and writes. For instance, if 2 out of 3 replicas or 3 out of 5 replicas are available, the tablet
+  is available.
++
+Reads can be serviced by read-only follower tablets, even in the event of a
+leader tablet failure.
 - Structured data model.
 
 By combining all of these properties, Kudu targets support for families of

http://git-wip-us.apache.org/repos/asf/incubator-kudu/blob/c6554caa/docs/release_notes.adoc
----------------------------------------------------------------------
diff --git a/docs/release_notes.adoc b/docs/release_notes.adoc
index b73be68..e8430dd 100644
--- a/docs/release_notes.adoc
+++ b/docs/release_notes.adoc
@@ -67,7 +67,7 @@ batchSizeBytes as is the corresponding property in AsyncKuduScanner. This makes
 consistent with the C++ client.
 . The "kudu-admin" tool can now list and delete tables via its new subcommands
 "list_tables" and "delete_table <table_name>".
-. OSX is now supported for single node development. Please consult its specific installation
+. OSX is now supported for single-host development. Please consult its specific installation
 instructions in link:installation.html#osx_from_source[OS X].
 
 The upgrade instructions are situated at link:installation.html#upgrade[Upgrade from 0.5.0 to 0.6.0].
@@ -196,7 +196,7 @@ link:kudu_impala_integration.html[Impala Integration] documentation.
 * To use Impala_Kudu alongside an existing Impala instance, you must install using parcels.
 * Updates, inserts, and deletes via Impala are non-transactional. If a query
 fails part of the way through, its partial effects will not be rolled back.
-* All queries will be distributed across all Impala nodes which host a replica
+* All queries will be distributed across all Impala hosts which host a replica
 of the target table(s), even if a predicate on a primary key could correctly
 restrict the query to a single tablet. This limits the maximum concurrency of
 short queries made via Impala.

http://git-wip-us.apache.org/repos/asf/incubator-kudu/blob/c6554caa/docs/transaction_semantics.adoc
----------------------------------------------------------------------
diff --git a/docs/transaction_semantics.adoc b/docs/transaction_semantics.adoc
index e3b91ef..b2c51c4 100644
--- a/docs/transaction_semantics.adoc
+++ b/docs/transaction_semantics.adoc
@@ -131,7 +131,7 @@ possibly assign a lower timestamp to a following write.
 For the moment, Kudu's experimental implementation of `Commit Wait` is only available
 in the java client, by setting `KuduSession#setExternalConsistencyMode()`
 to `COMMIT_WAIT`. When using this mode, the latency of writes is tightly
-tied to how accurate the clocks on all the cluster nodes are, and using this mode
+tied to the accuracy of clocks on all the cluster hosts, and using this mode
 with loose clock synchronization causes writes to take a long time to complete or even time
 out. See <<known_issues>>.