ReadClusterData Stage Optimisation : ZKCache added in getStat #68
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
The PR aims to optimise the ReadClusterData Stage of the rebalance pipeline in Helix. Customers with huge workloads are seeing significant increase in pipeline time. This PR is one of the item to improve on the performance of the Helix pieplines.
Description
getStats() method was not utilising the ZKCache, making direct ZooKeeper calls for every method call. This is causing the performance bottleneck in ReadClusterData Stage where a lot of time is spent on waiting for the ZK response. The changes added logic to utilise ZKCache.
Tests
Verified with the unit tests.
Changes that Break Backward Compatibility (Optional)
NA
Documentation (Optional)
NA
Commits
Code Quality
(helix-style-intellij.xml if IntelliJ IDE is used)