fix: async R2-backed export for large database dumps (fixes #59)#101
Open
bcornish1797 wants to merge 1 commit intoouterbase:mainfrom
Open
fix: async R2-backed export for large database dumps (fixes #59)#101bcornish1797 wants to merge 1 commit intoouterbase:mainfrom
bcornish1797 wants to merge 1 commit intoouterbase:mainfrom
Conversation
Fixes outerbase#59 - Add POST /export/dump for async dump initiation via DO alarm - Add GET /export/dump/:id for status polling - Add GET /export/dump/:id/download for streaming from R2 - Use DO alarms for multi-cycle processing of large databases - Use R2 multipart upload API to avoid memory limits - Keep existing GET /export/dump for small databases (backward compatible)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
POST /export/dumpkicks off a background job, returns{ dumpId, statusUrl }immediatelyGET /export/dump/:dumpIdto poll status/progressGET /export/dump/:dumpId/downloadstreams the completed dump file from R2GET /export/dump(sync path) is unchanged — still works for small databasesWhy
The current endpoint loads the whole database into memory and has to finish inside the 30-second Workers limit. That's fine for small databases but breaks for anything approaching the DO storage limit. The async path runs the export in chunks via DO alarms that chain themselves until done, then writes the result to R2 for streaming download.
Test
/claim #59