Repository navigation
Ensure all objects are installed into local storage when restoring from a snapshot - #6543
Conversation
57a24fe to
58d9cb4
Compare
|
I meant to check at the end of This would, however, make it possible for a database to crash-loop if the budget is smaller than what was allowed before the database restarted. |
Instead of crashing, we could also let the database come up. It will be queryable, but the eviction triggered by a write is likely going to throw a budget error -- which will be observable by the client. This is potentially better UX, and won't waste cycles repeatedly restarting the database. What do you think @joshua-spacetime? |
58d9cb4 to
5de6862
Compare
I'm in favor of this. It would also give users an opportunity to delete data right? |
Well maybe not if it can't allocate a temporary page for the deletes. |
684c19f to
7739c21
Compare
5de6862 to
5b59eed
Compare
a snapshot. This works by first installing all objects as resident, and then evicting until the low watermark is reached. Not yet optimal, as we could use hardlinks instead of flushing. The guarantee that a catalog entry that has a permit was written by the same storage instance allows to skip redundant writes.
5b59eed to
4788646
Compare
This works by first installing all objects as resident, and then evicting until the low watermark is reached.
Not yet optimal, as we could use hardlinks instead of flushing.
The guarantee that a catalog entry that has a permit was written by the same storage instance allows to skip redundant writes.
API and ABI breaking changes
N/A
Rollback safety impact
N/A
Expected complexity level and risk
2
Testing
Existing