Tim Burke c10f8ae4ec relinker: Track part_power/next_part_power in state file ...

...and only update from the state file if those part powers match the
work we're currently doing. Otherwise, we would skip relinking when
trying to do multiple increases in quick succession, causing misplaced
data that clients could not access.

Note that because the part_power/next_part_power pair *must* change
between relinking and cleanup, we now only need to track one boolean per
part; the state file will automatically reset when switching modes.

Also note that any state files in the old format will be discarded --
this is safe, but may cause increased I/O. OTOH, operators probably
shouldn't be upgrading Swift mid-part-power-increase anyway.

Change-Id: Id08d0893db2c6e6f9ce1e42a104409568daf985b
Closes-Bug: #1910589

2021-01-26 18:23:58 +00:00

19 KiB

Raw Blame History

View Raw