Skip to content
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.

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

Add a periodic background job to check the consistency of the index #2227

Closed
pietroalbini opened this issue Feb 26, 2020 · 1 comment
Closed
Labels
C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear

Comments

@pietroalbini
Copy link
Member

Currently we have no way to get paged if we lose consistency between the crates.io database and the git index. Having such alerts would improve the team's response time to outages like 2020-02-20.

The job should run periodically, with an high enough frequency to produce actionable alerts but a low enough frequency to avoid disruptions to other jobs in the queue. Also, it should ignore crates in the database still waiting for the background job pushing the index commit to execute (we already have separate alerts if those jobs stay in the queue too much).

@Turbo87 Turbo87 added C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear and removed A-internal labels Feb 11, 2021
@Turbo87
Copy link
Member

Turbo87 commented Aug 3, 2023

At this point we are generating the index files completely from the database content, so unless an index sync job repeatedly fails (which would trigger the on-call team) the index should not get out of sync anymore.

@Turbo87 Turbo87 closed this as completed Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear
Projects
None yet
Development

No branches or pull requests

2 participants