Persist Auctioneer Bid DB to S3 #2745
Merged
Conversation
This file contains 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
cla-bot
bot
added
the
s
ganeshvanahalli
requested review from
Tristan-Wilson,
diegoximenes and
magicxyyz
Tristan-Wilson
requested changes
Nov 20, 2024
…nt duplicate uploads
Tristan-Wilson
requested changes
Dec 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR enables auctioneer to persist validated bids, that are currently stored in a local SQLite database to AWS S3.
We introduce S3StorageService configurable via
--auctioneer-server.s3-storage.*config options, that when enabled, will periodically (via--auctioneer-server.s3-storage.upload-interval) upload validated bids from local db to the configured aws S3 bucket and upon success- removes these bids from the local db.The bids are uploaded in batches in the form of csv files compressed with gzip. The file name would be
Resolves NIT-2783