datastore driver - adding reconnect to datastore capabilities #2969
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.
Signed-off-by: riccardomodanese riccardo.modanese@eurotech.com
There is no way to start the broker if ElasticSearch is down at startup. The broker is expected to start even if ES is down. The connection with the data-store should be tried periodically, until it has been established
Related Issue
none
Description of the solution adopted
No exception is thrown if an error occurred when establishing the data-store connection. A connection task is then executed periodically until the connection is established.
Screenshots
none
Any side note on the changes made
none