HDDS-628. Fix outdated names used in HDDS documentations.
This commit is contained in:
parent
bca928d3c7
commit
5da042227c
|
@ -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
|
||||
|
|
|
@ -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();
|
||||
|
|
|
@ -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.
|
||||
|
||||
|
|
|
@ -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.
|
||||
|
||||
|
|
Loading…
Reference in New Issue