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

Improve client partition table update push mechanism #16939

Merged
merged 1 commit into from May 4, 2020
Merged

Improve client partition table update push mechanism #16939

merged 1 commit into from May 4, 2020

Commits on Apr 29, 2020

  1. Improve client partition table update push mechanism 

    When a partition table update is detected, a member pushes
updated partition table to its clients.

When there are many clients (hundreds or more), partition table updates
cause big latencies in migration system. Reason is, partition service's lock must be acquired
to create partition table's latest view and this is called on every partition update.

To fix that, we can skip some intermediate partition table updates. There's no need to push every update,
because once partition table updates begin, generally there'll be many. Most of them will be stale
in a short time. It's fine to skip some to reduce push frequency and lock contention.
    @mdogan
    mdogan committed Apr 29, 2020
    Configuration menu
    Copy the full SHA
    d174012 View commit details
    Browse the repository at this point in the history