Repository: hadoop Updated Branches: refs/heads/trunk bca928d3c -> 5da042227
HDDS-628. Fix outdated names used in HDDS documentations. Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/5da04222 Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/5da04222 Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/5da04222 Branch: refs/heads/trunk Commit: 5da042227cfce440eddc263b377a70ed5b3743fb Parents: bca928d Author: Yiqun Lin <yq...@apache.org> Authored: Fri Oct 12 14:00:13 2018 +0800 Committer: Yiqun Lin <yq...@apache.org> Committed: Fri Oct 12 14:00:13 2018 +0800 ---------------------------------------------------------------------- hadoop-ozone/docs/content/Dozone.md | 4 ++-- hadoop-ozone/docs/content/JavaApi.md | 2 +- hadoop-ozone/docs/content/OzoneManager.md | 2 +- hadoop-ozone/docs/content/Settings.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/hadoop/blob/5da04222/hadoop-ozone/docs/content/Dozone.md ---------------------------------------------------------------------- diff --git a/hadoop-ozone/docs/content/Dozone.md b/hadoop-ozone/docs/content/Dozone.md index 7906cf3..f6efb0f 100644 --- a/hadoop-ozone/docs/content/Dozone.md +++ b/hadoop-ozone/docs/content/Dozone.md @@ -63,14 +63,14 @@ Useful Docker & Ozone Commands If you make any modifications to ozone, the simplest way to test it is to run freon and unit tests. -Here are the instructions to run corona in a docker based cluster. +Here are the instructions to run freon in a docker based cluster. {{< highlight bash >}} docker-compose exec datanode bash {{< /highlight >}} This will open a bash shell on the data node container. -Now we can execute corona for load generation. +Now we can execute freon for load generation. {{< highlight bash >}} ozone freon randomkeys --numOfVolumes=10 --numOfBuckets 10 --numOfKeys 10 http://git-wip-us.apache.org/repos/asf/hadoop/blob/5da04222/hadoop-ozone/docs/content/JavaApi.md ---------------------------------------------------------------------- diff --git a/hadoop-ozone/docs/content/JavaApi.md b/hadoop-ozone/docs/content/JavaApi.md index 1d32bed..e538f4b 100644 --- a/hadoop-ozone/docs/content/JavaApi.md +++ b/hadoop-ozone/docs/content/JavaApi.md @@ -42,7 +42,7 @@ can use OzoneClient ozClient = OzoneClientFactory.getRestClient(); {{< /highlight >}} -And to get a a RPC client we can call +And to get a RPC client we can call {{< highlight java >}} OzoneClient ozClient = OzoneClientFactory.getRpcClient(); http://git-wip-us.apache.org/repos/asf/hadoop/blob/5da04222/hadoop-ozone/docs/content/OzoneManager.md ---------------------------------------------------------------------- diff --git a/hadoop-ozone/docs/content/OzoneManager.md b/hadoop-ozone/docs/content/OzoneManager.md index 560f827..5eb8663 100644 --- a/hadoop-ozone/docs/content/OzoneManager.md +++ b/hadoop-ozone/docs/content/OzoneManager.md @@ -70,7 +70,7 @@ We are hopeful that this leads to a more straightforward way of discovering sett OM and SCM ------------------- [Storage container manager]({{< ref "Hdds.md" >}}) or (SCM) is the block manager - for ozone. When a client requests OM for a set of data nodes to write data, OM talk to SCM and gets a block. + for ozone. When a client requests OM for a set of data nodes to write data, OM talks to SCM and gets a block. A block returned by SCM contains a pipeline, which is a set of nodes that we participate in that block replication. http://git-wip-us.apache.org/repos/asf/hadoop/blob/5da04222/hadoop-ozone/docs/content/Settings.md ---------------------------------------------------------------------- diff --git a/hadoop-ozone/docs/content/Settings.md b/hadoop-ozone/docs/content/Settings.md index 41ab04a..5c9bb41 100644 --- a/hadoop-ozone/docs/content/Settings.md +++ b/hadoop-ozone/docs/content/Settings.md @@ -43,7 +43,7 @@ requests blocks from SCM, to which clients can write data. ## Setting up an Ozone only cluster -* Please untar the ozone-0.2.1-SNAPSHOT to the directory where you are going +* Please untar the ozone-<version> to the directory where you are going to run Ozone from. We need Ozone jars on all machines in the cluster. So you need to do this on all machines in the cluster. --------------------------------------------------------------------- To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-commits-h...@hadoop.apache.org
