-
Notifications
You must be signed in to change notification settings - Fork 251
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantprovider
Description
Follow up to #1159
To allow consistent provide operations, the provide queue should be persisted on shutdown to allow resuming provides after a restart.
This is necessary for keys in the provide queue, not belonging to a region that is late for reprovide at the time of the restart. Not persisting the queue implies that keys in the provide queue would need to wait up to reprovideInterval - downTime
before being provided for the first time.
If a queued key belong to a region that is late for reprovide on restart, then it will be provided as part of the region reprovide, which will happen ASAP.
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantprovider