Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Doc - Clustering docs typos (#8827)

This commit is contained in:
Simran 2019-04-23 13:56:17 +02:00 committed by GitHub
parent 7d2a920707
commit b5d79a8a1d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/Books/Manual/Administration/Cluster/README.md
View File

@ -177,15 +177,15 @@ Replacing/Removing a _DBServer_
-------------------------------
_DBServers_ are where the data of an ArangoDB cluster is stored. They
do not publish a we UI and are not meant to be accessed by any other
do not publish a web UI and are not meant to be accessed by any other
entity than _Coordinators_ to perform client requests or other _DBServers_
to uphold replication and resilience.
The clean way of removing a _DBServer_ is to first releave it of all
The clean way of removing a _DBServer_ is to first relieve it of all
its responsibilities for shards. This applies to _followers_ as well as
_leaders_ of shards. The requirement for this operation is that no
collection in any of the databases has a `relicationFactor` greater or
equal to the current number of _DBServers_ minus one. For the pupose of
equal to the current number of _DBServers_ minus one. For the purpose of
cleaning out `DBServer004` for example would work as follows, when
issued to any _Coordinator_ of the cluster:
@ -193,7 +193,7 @@ issued to any _Coordinator_ of the cluster:
After the _DBServer_ has been cleaned out, you will find a trash bin
icon to the right of the name of the _DBServer_ on any _Coordinators_'
UI. Clicking on it will remove the _DBServer_ in questiuon from the
UI. Clicking on it will remove the _DBServer_ in question from the
cluster.
Firing up any _DBServer_ from a clean data directory by specifying the