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

Submit jobs before checking status #471

Closed
donkirkby opened this issue May 22, 2019 · 0 comments
Closed

Submit jobs before checking status #471

donkirkby opened this issue May 22, 2019 · 0 comments
Assignees

Comments

@donkirkby
Copy link
Member

Particularly when reprocessing old runs, the number of active jobs can dip well below the configured maximum. It looks like the queue gets full, then the find_samples() thread notices that it's been over an hour since it scanned for new runs, and it has to recheck all the samples in the active run folders. It's also checking the status of all the active samples between each sample recheck, so it can take over an hour to finish the rescan.

Suggested fix: don't check the status of active samples, if a new sample has just been added, and maybe use a larger queue for folder events.

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

No branches or pull requests

1 participant