[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

[DocDB] Remove delay for load balancer after leader failover #24937

Open
1 task done
druzac opened this issue Nov 15, 2024 · 0 comments
Open
1 task done

[DocDB] Remove delay for load balancer after leader failover #24937

druzac opened this issue Nov 15, 2024 · 0 comments
Assignees
@druzac
Labels
area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue

Comments

@druzac
Copy link
Contributor
druzac commented Nov 15, 2024 •
edited by jira bot
Loading

Jira Link: DB-14077

Description

The load balancer is not run for the first two minutes after a master leader becomes leader:

yugabyte-db/src/yb/master/catalog_manager_bg_tasks.cc

Lines 261 to 262 in b4b3a40

if (catalog_manager_->TimeSinceElectedLeader() >
MonoDelta::FromSeconds(FLAGS_load_balancer_initial_delay_secs)) {

This delay is to wait for the new master leader to receive initial heartbeats from tablet servers. However when the persisted tablet server registry (#22925) is active the full membership of tablet servers in the cluster is available from the sys catalog so new master leaders no longer need to wait for so long. Instead a new master leader could start running the load balancer as soon as it has received a heartbeat from every tablet server considered LIVE in the registry. This should be a few seconds in the common case.

Issue Type

kind/enhancement

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@druzac druzac added area/docdb YugabyteDB core features status/awaiting-triage Issue awaiting triage labels Nov 15, 2024
@yugabyte-ci yugabyte-ci added kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue labels Nov 15, 2024
@druzac druzac self-assigned this Nov 15, 2024
@yugabyte-ci yugabyte-ci removed the status/awaiting-triage Issue awaiting triage label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@druzac druzac

Labels
area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@druzac @yugabyte-ci