This is an automated email from the ASF dual-hosted git repository.
neoyang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone.git
The following commit(s) were added to refs/heads/master by this push:
new bc49c45 HDDS-4682. Fix several typos in docs (#1787)
bc49c45 is described below
commit bc49c45a4cf2ee48e39047c038a11773e47326fa
Author: lamber-ken <[email protected]>
AuthorDate: Thu Jan 14 11:18:08 2021 +0800
HDDS-4682. Fix several typos in docs (#1787)
---
hadoop-hdds/docs/content/design/decommissioning.md | 10 +++++-----
hadoop-hdds/docs/content/tools/AuditParser.md | 2 +-
hadoop-ozone/dist/src/main/compose/ozone/README.md | 2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/hadoop-hdds/docs/content/design/decommissioning.md
b/hadoop-hdds/docs/content/design/decommissioning.md
index 6c8e08e..e4abdf6 100644
--- a/hadoop-hdds/docs/content/design/decommissioning.md
+++ b/hadoop-hdds/docs/content/design/decommissioning.md
@@ -36,7 +36,7 @@ Goals:
* The progress of the decommissioning should be trackable
* The nodes under decommissioning / maintenance mode should not been used for
new pipelines / containers
* The state of the datanodes should be persisted / replicated by the SCM (in
HDFS the decommissioning info exclude/include lists are replicated manually by
the admin). If datanode is marked for decommissioning this state be available
after SCM and/or Datanode restarts.
- * We need to support validations before decommissioing (but the violations
can be ignored by the admin).
+ * We need to support validations before decommissioning (but the violations
can be ignored by the admin).
* The administrator should be notified when a node can be turned off.
* The maintenance mode can be time constrained: if the node marked for
maintenance for 1 week and the node is not up after one week, the containers
should be considered as lost (DEAD node) and should be replicated.
@@ -128,7 +128,7 @@ One other difference with maintenance mode and
decommissioning, is that you must
STALE | Some heartbeats were missing for an already missing
nodes.
DEAD | The stale node has not been recovered.
ENTERING_MAINTENANCE | The in-progress state, scheduling is disabled but the
node can't not been turned off due to in-progress replication.
- IN_MAINTENANCE | Node can be turned off but we expecteed to get it
back and have all the replicas.
+ IN_MAINTENANCE | Node can be turned off but we expected to get it back
and have all the replicas.
DECOMMISSIONING | The in-progress state, scheduling is disabled, all
the containers should be replicated to other nodes.
DECOMMISSIONED | The node can be turned off, all the containers are
replicated to other machine
@@ -148,7 +148,7 @@ The Algorithm is pretty simple from the Decommission or
Maintenance point of vie
* Container is closed.
* We have at least one HEALTHY copy at all times.
- * For entering DECOMMISSIONED mode `maintenance + healthy` must equal to
`expectedeCount`
+ * For entering DECOMMISSIONED mode `maintenance + healthy` must equal to
`expectedCount`
5. We will update the node state to DECOMMISSIONED or IN_MAINTENANCE reached
state.
@@ -186,7 +186,7 @@ Replica count = expectedCount - currentCount
In case the _Replica count_ is positive, it means that we need to make more
replicas. If the number is negative, it means that we are over replicated and
we need to remove some replicas of this container. If the Replica count for a
container is zero; it means that we have the expected number of containers in
the cluster.
-To support idempontent placement strategies we should substract the in-fligt
replications from the result: If there are one in-flight replication process
and two replicas we won't start a new replication command unless the original
command is timed out. The timeout is configured with
`hdds.scm.replication.event.timeout` and the default value is 10 minutes.
+To support idempotent placement strategies we should subtract the in-flight
replications from the result: If there are one in-flight replication process
and two replicas we won't start a new replication command unless the original
command is timed out. The timeout is configured with
`hdds.scm.replication.event.timeout` and the default value is 10 minutes.
More preciously the current algorithm is the following:
@@ -249,7 +249,7 @@ The following conditions should be true for all the
containers and all the conta
**From DECOMMISSIONING to DECOMMISSIONED**:
* There are at least one healthy replica
- * We have three replicas (both helthy and maintenance)
+ * We have three replicas (both healthy and maintenance)
Which means that our stop condition can be formalized as:
diff --git a/hadoop-hdds/docs/content/tools/AuditParser.md
b/hadoop-hdds/docs/content/tools/AuditParser.md
index e4da208..ee2acd9 100644
--- a/hadoop-hdds/docs/content/tools/AuditParser.md
+++ b/hadoop-hdds/docs/content/tools/AuditParser.md
@@ -21,7 +21,7 @@ summary: Audit Parser tool can be used for querying the ozone
audit logs.
-->
Audit Parser tool can be used for querying the ozone audit logs.
-This tool creates a sqllite database at the specified path. If the database
+This tool creates a sqlite database at the specified path. If the database
already exists, it will avoid creating a database.
The database contains only one table called `audit` defined as:
diff --git a/hadoop-ozone/dist/src/main/compose/ozone/README.md
b/hadoop-ozone/dist/src/main/compose/ozone/README.md
index c28f832..7ffce11 100644
--- a/hadoop-ozone/dist/src/main/compose/ozone/README.md
+++ b/hadoop-ozone/dist/src/main/compose/ozone/README.md
@@ -18,7 +18,7 @@ This directory contains a docker-compose definition for an
Ozone cluster with al
There are two optional add-ons:
- * monitoring: adds Grafana, Jaeger and Prometheus sercvies, and configures
Ozone to work with them
+ * monitoring: adds Grafana, Jaeger and Prometheus services, and configures
Ozone to work with them
* profiling: allows sampling Ozone CPU/memory using
[async-profiler](https://github.com/jvm-profiling-tools/async-profiler)
## How to start
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
