Skip to content

[WIP] Populate each service's data separately #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

[WIP] Populate each service's data separately #50

wants to merge 6 commits into from

Conversation

BenMusch
Copy link
Contributor

Right now, billow updates can take hours (or days) because of the size and rate limiting on our account. If a single stage in a job fails, the entire update fails and prevents any data from syncing.

This PR refactors the system so that each AWS service's data updates in its own job, so EC2 queries failing won't impact RDS data collection. A full initial build is still required on startup so we don't end up with an incomplete view of the data, but afterwards the services will update incrementally

Reviewers

@jtai @erluoli
@BenMusch
Copy link
Contributor Author

Sadly this does not seem to actually improve things in testing 😞 Will leave it running for a couple days to see
@BenMusch
Copy link
Contributor Author

Update: Does seem to be helping after some time. I also tweaked the refresh rate to be lower to avoid hammering the API
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
@BenMusch @jtai