Disable persistency on ArangoDB by default #90
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
…t to the database
…raction operations
…ency-by-default Fixes by autopep8 action
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
When trying to launch the controller with the ENABLE_PERSITENCY configuration parameter set, the controller tries to establish a connection to the ArangoDB Docker container. In the ROSE VM v2.7 by default the Docker infrastructure is disabled and ArangoDB container is not reachable. This results in a connection error when the controller tries to connect to ArangoDB.
This PR disables the controller persistency in the default configuration file and fixes some persistence issues.
Persistence can still be enabled by running the Docker stack and setting the ENABLE_PERSISTENCY parameter in the configuration file.