Skip to content
This repository has been archived by the owner on Apr 1, 2024. It is now read-only.

ISSUE-17860: [feature] Add Metrics to understand Load Balancing Decisions #4936

Open
1 of 2 tasks
sijie opened this issue Sep 28, 2022 · 0 comments
Open
1 of 2 tasks
Labels

Comments

@sijie
Copy link
Member

sijie commented Sep 28, 2022

Original Issue: apache#17860


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 apache#16691

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@sijie sijie added the Stale label Oct 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant