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

versions repo sharding #1172

Closed
michielbdejong opened this issue Sep 13, 2024 · 2 comments
Closed

versions repo sharding #1172

michielbdejong opened this issue Sep 13, 2024 · 2 comments

Comments

@michielbdejong
Copy link
Member

Since our snapshots and versions repos are so big, for robustness, I think we need to shard them into multiple smaller ones (e.g. one for each letter of the alphabet, or e.g. 100 repos sharding based on mod of hash of service name)

@michielbdejong michielbdejong changed the title versions and snapshots repo sharding versions repo sharding Sep 16, 2024
@michielbdejong
Copy link
Member Author

Now that we're running without snapshots thanks to OpenTermsArchive/engine#1104 this would only apply to the versions repo.

A simpler thing to do would be to give the npx ota track command extra options to filter and shard on service name hash, or at least to start (and finish) in a random place in the alphabet.

michielbdejong added a commit to tosdr/ota-engine that referenced this issue Sep 16, 2024
@michielbdejong
Copy link
Member Author

I shared the cron job instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant