[Bugfix] Quick checking ArangoSync availability #1188
Merged
Conversation
This file contains hidden or 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
nikita-vanyasin
approved these changes
Nov 21, 2022
Co-authored-by: Nikita Vaniasin <nikita.vanyasin@gmail.com>
jwierzbo
approved these changes
Nov 21, 2022
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.
During tests I found that ArangoSync master was not UP for long time, because replication was in initial-sync. In case of OpSec it takes 2 hours to change this state into running. Operator waits for running state and after 30 minutes gives up and then it starts next ArangoSync master. If CPU, memory resources are not sufficient then master is killed before 30 minutes, and replication never can reach running state.
I have changed
Healthendpoint intoVersionthanks to that ArangoSync is immediately responsive.