Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[topicmappr] handle larger metrics data in ZooKeeper #258

Closed
jamiealquiza opened this issue Jun 3, 2019 · 1 comment · Fixed by #264
Closed

[topicmappr] handle larger metrics data in ZooKeeper #258

jamiealquiza opened this issue Jun 3, 2019 · 1 comment · Fixed by #264

Comments

@jamiealquiza
Copy link
Collaborator

Currently, topicmappr operations that rely on metrics data (any rebalance command or rebuild with the storage placement option) read data from ZooKeeper. It's desirable to keep this input as the canonical source of this data for now.

One issue is that the current structure just blobs all of the topic/partition size data as a single json key, which can be quite large in clusters with many topics/partitions. We should version the data structure format and introduce a new type that utilizes compression or other ways to cope with very large inputs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant