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

[v23.1.x] r/configuration_manager: add highest_known_offset checkpoint mutex #9960

Merged
merged 2 commits into from
Apr 12, 2023
Merged

[v23.1.x] r/configuration_manager: add highest_known_offset checkpoint mutex #9960

merged 2 commits into from
Apr 12, 2023

Commits on Apr 11, 2023

  1. r/configuration_manager: prevent concurrent checkpoint attempts 

    Previously, several background fibers spawned by consensus::disk_append
could run configuration_manager::maybe_store_highest_known_offset in
parallel. Because the storage_resources units were not released until we
actually finished the kvstore write, every bg fiber launched during the
kvstore debounce period will do a kvstore write on its own. This commit
adds a flag that makes sure that we do only one checkpoint at a time.

Fixes redpanda-data#9309

(cherry picked from commit 17df605)
    @ztlpn
    ztlpn committed Apr 11, 2023
    Configuration menu
    Copy the full SHA
    61c0962 View commit details
    Browse the repository at this point in the history

  2. r/offset_translator: skip concurrent checkpoint attempts 

    (cherry picked from commit ec8f387)
    @ztlpn
    ztlpn committed Apr 11, 2023
    Configuration menu
    Copy the full SHA
    ca2cde5 View commit details
    Browse the repository at this point in the history