Use a separate ClusterParticipant for Stats Aggregation in Ambry
Open
@jsjtzyy is already working on this.
Since Jan 4, 2019.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
Currently the stats aggregation relies on HelixParticipant and sort of depends on same ZKHelixManager. A separate ClusterParticipant and an independent ZKHelixManager could be set up for stats aggregation. Thus, stats aggregation could work no matter `StaticClusterManager` or `HelixClusterManager` is being used.
Another benefit we may get is, for HelixParticipant, it can participate earlier which may avoid race conditions. (Currently we add extra lock to eliminate such race condition)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.