Process crash recovery #168
Open
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
…iners and kill them to provok crash and verify failover algorthms etc..
…process in own process
…emented & running !
| } catch (IOException e) { | ||
| logger.info("Failed to write in local db: " + e); | ||
| } | ||
| } |
There was a problem hiding this comment.
This code is repeated in the Exchange, Monitor and ScalingProcess. It should probably be just a function call.
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 pull request contains the second milestone about the HA for RoQ.
The following code implements the features to monitor and recover the processes (monitor, exchange, scalingprocess) which run on a slave (at the exception of the HCM which is monitored by the GCM).