-
Notifications
You must be signed in to change notification settings - Fork 82
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
Index v2 repositories #118
Comments
Indexing process crashed after some hours (or minutes if used more than 8 threads) with Now the process is running in a batch job using a local node directory as The current process uses 16 threads and is currently using 27 Gb of ram, far from the 64 Gb limit from the pod. |
Fingers crossed! |
Indexing has been running since last Tuesday (May 14th) in 5 nodes. Repositories are split in batches of 5000 and each. Each node processes 10 batches except for the first one (does not have limit) and the last one that processes 13 batches. In total there are 53 batches. Here's the number of lines in each batch index:
Files The first node appears to have finished (10-19) and pods indexing batches from 20 to 53 are stuck in the middle of their lists. Every day the jobs are checked at least twice as some repositories get stuck processing so the next batch is not started. These jobs are killed to let the next batch run. Kills are done with
There are also some repositories that had some kind of error and could not be processed as seen in the index lists. If all of the batch was processed correctly they should count |
@jfontan I guess that this is done. |
Long overdue but we still have to add documentation on the indexing process. |
Requires #117
The text was updated successfully, but these errors were encountered: