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

[feature] Add Metrics to understand Load Balancing Decisions #17860

Open
1 of 2 tasks
dave2wave opened this issue Sep 27, 2022 · 1 comment
Open
1 of 2 tasks

[feature] Add Metrics to understand Load Balancing Decisions #17860

dave2wave opened this issue Sep 27, 2022 · 1 comment
Labels

Comments

@dave2wave
Copy link
Member

dave2wave commented Sep 27, 2022

Search before asking

  • I searched in the issues and found nothing similar.

Motivation

When pushing pulsar clusters to see maximum performance it is important to understand which metric is causing bundle splits and unloading. The metrics shared only show that the split and/or unload occurred.

  1. bundle unload metrics
  2. bundle split metrics

The logs give values, but it is hard to reason about these or monitor them.

Solution

Add reason counts for load balancing: bundle splits, and unloads.

  1. Bandwidth
  2. CPU
  3. Direct Memory
  4. Memory
  5. Admin

Alternatives

Make the log files be much clearer about which metric has triggered a bundle split or unload.

Anything else?

This is related to #16691

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@dave2wave dave2wave changed the title Add Metrics to understand Load Balancing Decisions [feature] Add Metrics to understand Load Balancing Decisions Sep 27, 2022
@github-actions
Copy link

The issue had no activity for 30 days, mark with Stale label.

@github-actions github-actions bot added the Stale label Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant