Improving documentation #170
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
neunhoef
approved these changes
Jun 11, 2018
| The exception to this is cursor related requests made to an ArangoDB `Cluster` deployment. | ||
| The coordinator that handles an initial query request (that results in a `Cursor`) | ||
| will save some in-memory state in that coordinator, if the result of the query | ||
| is to big to be transfer back in the response of the initial request. |
| Kubernetes cluster and synchronize your endpoints before making the | ||
| initial query request. | ||
| This will result in the use (by the driver) of internal DNS names of all coordinators. | ||
| A follow-up request can then be send to exaclty the same coordinator. |
There was a problem hiding this comment.
"send" -> "sent"
"exaclty" -> "exactly"
| @@ -10,13 +10,45 @@ In the `ArangoDeployment` resource, one can specify the type of storage | |||
| used by groups of servers using the `spec.<group>.storageClassName` | |||
| setting. | |||
|
|
|||
| This is an example of a `Cluster` deployment that stores its agent & dbserver | |||
| data on `PersistentVolumes` that using the `my-local-ssd` `StorageClass` | |||
| in Kubernetes. | ||
| These logs are accessible through the `Pods` that group these containers. | ||
|
|
||
| The fetch the logs of the default container running in a `Pod`, run: |
|
|
||
| ```bash | ||
| kubectl logs <pod-name> -n <namespace> | ||
| # or with follow option to keep inspecting logs while their are written |
|
|
||
| There are two common causes for this. | ||
|
|
||
| 1) The `Pods` cannot be scheduled because there are no enough nodes available. |
|
|
||
| - If an `Agent` was using the volume, it can be repaired as long as 2 other agents are still healthy. | ||
| - If a `DBServer` was using the volume, and the replication factor of all database | ||
| collections is 2 of higher, and the remaining dbservers are still healthy, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains several improvements, fixes & extensions of the manual.