Skip to content

Conversation

@TakaHiR07
Copy link
Contributor

@TakaHiR07 TakaHiR07 commented Mar 27, 2024

Motivation

Implement bookie load balance to avoid bookie high write latency problem.

Master issue: #4247

Changes

The proposed changes involves:

  1. Implement BaseMetricMonitor in bookie server, which would collect bookie load information periodically
  2. bookie client continue to use getBookieInfo restApi to acquire load information from each bookie.
  3. modify the implementation of RackawareEnsemblePlacementPolicyImpl, support select ensemble by LoadWeightBasedPlacement. Since LoadWeightBasedPlacement is an enhancement of DiskWeightBasedPlacement, it would cover the DiskWeightBasedPlacement if feature enable.

If this PR is a BookKeeper Proposal (BP):

  • Make sure the PR title is formatted like:
    <BP-#>: Description of bookkeeper proposal
    e.g. BP-1: 64 bits ledger is support
  • Attach the master issue link in the description of this PR.
  • Attach the google doc link if the BP is written in Google Doc.

optional int32 journalIoUtil = 4;
optional int32 ledgerIoUtil = 5;
optional int32 cpuUsedRate = 6;
optional int64 writeBytePerSecond = 7;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shall we name it writeBytesPerSecond?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants