pulsar icon indicating copy to clipboard operation
pulsar copied to clipboard

[feat] [broker] support broker isolation for uniform load shedder strategy

Open rdhabalia opened this issue 4 years ago • 12 comments

Motivation

We added Uniform load balancer strategy in #12902 which considers all the brokers and distributes the load uniformly across all available brokers. However, it doesn't consider namespace isolation policies where we want to uniformly distribute load across brokers which are part of same isolation group. This PR supports namespace isolation and distribute load across that subset of brokers based on their isolation group.

Modification

UniformLoadShedder prepares group of brokers which are part of isolation policy and try to find out bundle-candidate such a way it uniformly distributes load across that prepared group.

Result

UniformLoadShedder considers namespace isolation policy while distributing the load.

rdhabalia avatar Dec 02 '21 03:12 rdhabalia

@rdhabalia:Thanks for your contribution. For this PR, do we need to update docs? (The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

github-actions[bot] avatar Dec 02 '21 03:12 github-actions[bot]

@rdhabalia:Thanks for your contribution. For this PR, do we need to update docs? (The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

github-actions[bot] avatar Dec 02 '21 03:12 github-actions[bot]

@rdhabalia for the doc side, will you add explanations here?

Anonymitaet avatar Dec 02 '21 09:12 Anonymitaet

@Anonymitaet it's just an internal handling and it will not require any additional documentation

rdhabalia avatar Dec 02 '21 19:12 rdhabalia

When the traffic to be unloaded is too small, there is no need to unload at this time to avoid unnecessary unload:https://github.com/apache/pulsar/pull/13140

lordcheng10 avatar Dec 07 '21 06:12 lordcheng10

ping.

rdhabalia avatar Dec 20 '21 19:12 rdhabalia

@codelipenghui this PR was created 2 months back and ready to merge then why did you move to 2.11 release?

rdhabalia avatar Feb 09 '22 17:02 rdhabalia

this is not acceptable

rdhabalia avatar Feb 09 '22 17:02 rdhabalia

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

github-actions[bot] avatar Mar 12 '22 01:03 github-actions[bot]

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

github-actions[bot] avatar May 31 '22 02:05 github-actions[bot]

Since we will start the RC version of 3.0.0 on 2023-04-11, I will change the label/milestone of PR who have not been merged.

  • The PR of type feature is deferred to 3.1.0
  • The PR of type fix is deferred to 3.0.1

So drag this PR to 3.1.0

poorbarcode avatar Apr 10 '23 07:04 poorbarcode

@rdhabalia Please add the following content to your PR description and select a checkbox:

- [ ] `doc` <!-- Your PR contains doc changes -->
- [ ] `doc-required` <!-- Your PR changes impact docs and you will update later -->
- [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [ ] `doc-complete` <!-- Docs have been already added -->

github-actions[bot] avatar Apr 10 '23 07:04 github-actions[bot]