Fix instanceTopologyMap creation noisy logs #2688
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.
Issues
Description
When DOMAIN has more kv pairs than the ones required in TOPOLOGY(non-WAGED cases only), we log an incorrect warn message. When there are extra kv pairs, this check to see if numOfMatchedKeys == domainAsMap.size() is false because not all keys in DOMAIN are used.
This leads to huge log flooding. The check above is incorrect, as it should be okay to have extra kv pairs in DOMAIN as long as the required kv pairs exist. The check should be (numOfMatchedKeys < clusterTopologyConfig.getTopologyKeyDefaultValue().size()), so it only warns if DOMAIN does not contain the required topology keys.
Tests
Current tests should cover this.
Changes that Break Backward Compatibility (Optional)
NA
Documentation (Optional)
NA
Commits
Code Quality
(helix-style-intellij.xml if IntelliJ IDE is used)