This repository has been archived by the owner on Feb 9, 2021. It is now read-only.
added monitor capabilities to support configuration update in clustered ... #5
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.
...environment - currently deployments only
Extension to ConfigurationService to monitor underlying system repository for changes. In case a change is discovered notifies interested parties to perform update. Currently this mechanism is only used by deployments config service to be able to propagate deployments across cluster, once git repository is synchronized monitor will trigger runtime changes so all servers in the cluster will becomes in sync.
Monitor is enabled by default but can be disabled with system property. Interval of how often monitor checks the repository is also configurable - by default 2 secs.
Monitor checks the last modified date of a single file that is updated on every configuration change.