Fix for per node allocation strategy #5
Merged
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.
Description:
Fixing the reported issue with per node allocation strategy, where after adding / removing nodes the TA stopped assigning targets to collectors.
This was caused primarily by an issue in the watcher, where the node name is not always available, causing the node name to miss from the collector configuration, in turn causing the misconfiguration in TA and failure to assign targets. This is being fixed by restarting the watcher to ensure we wait until the node name is available in the spec of the collector.
Link to tracking Issue: https://coralogix.atlassian.net/browse/ES-178
Testing: Manually