@@ -97,7 +97,7 @@ collection and see the details about shards. Please keep in
9797mind that this has to be done ** for each database** separately!
9898
9999Obviously, this might be tedious and calls for automation. Therefore, there
100- are APIs for this. The first one is [ Cluster Health] ( ../../../HTTP/Cluster/Health .html) :
100+ are APIs for this. The first one is [ Cluster Health] ( https://www.arangodb.com/docs/stable/http/cluster-health .html) :
101101
102102```
103103POST /_admin/cluster/health
@@ -163,7 +163,7 @@ curl -k https://arangodb.9hoeffer.de:8529/_admin/cluster/health --user root: | j
163163```
164164
165165For the shards being in sync there is the
166- [ Cluster Inventory] ( ../../../HTTP/Replications/ReplicationDump .html#return-cluster-inventory-of-collections-and-indexes)
166+ [ Cluster Inventory] ( https://www.arangodb.com/docs/stable/http/replications-replication-dump .html#return-cluster-inventory-of-collections-and-indexes)
167167API call:
168168
169169```
@@ -446,7 +446,7 @@ above.
446446Finally, it is likely that the shard distribution in the "new" cluster
447447is not balanced out. In particular, the new _ DBSserver_ is not automatically
448448used to store shards. We recommend to
449- [ re-balance] ( ../../Administration/Cluster/README.md #movingrebalancing-shards) the shard distribution,
449+ [ re-balance] ( https://www.arangodb.com/docs/stable/administration-cluster.html #movingrebalancing-shards) the shard distribution,
450450either manually by moving shards or by using the _ Rebalance Shards_
451451button in the _ Shards_ tab under _ NODES_ in the web UI. This redistribution can take
452452some time again and progress can be monitored in the UI.
0 commit comments