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 Request: Prefer longer running replicas for PRS #15946

Open
GuptaManan100 opened this issue May 15, 2024 · 0 comments
Open

Feature Request: Prefer longer running replicas for PRS #15946

GuptaManan100 opened this issue May 15, 2024 · 0 comments

Comments

@GuptaManan100
Copy link
Member

Feature Description

When PRS-ing currently if all the replicas are caught up, we semi-randomly select one of them. This is non-optimal for large instances, we want to reparent to the replica that has been up for the longest (i.e. has had more time to warm its buffer pool from a possible innodb buffer pool dump upon shutdown). In a typical deployment scenario, the replica with longer uptime might have been running a minute or two longer than the other eligible replica. This isn't much, but that is enough time to load up 5-10 GB or more (depending on volume IOPs) of the buffer pool than the replica with shorter uptime. This enables the replica with longer uptime to immediately perform (potentially significantly) better than the other replica if it is promoted to primary.

Use Case(s)

Better performance from the new primary selected after PRS.

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

No branches or pull requests

1 participant