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

Retry logic for externals #2066

Open
Donaim opened this issue Oct 25, 2024 · 0 comments
Open

Retry logic for externals #2066

Donaim opened this issue Oct 25, 2024 · 0 comments

Comments

@Donaim
Copy link
Member

Donaim commented Oct 25, 2024

Kive is designed to run on clusters, and as such, it should acknowledge occasional connectivity failures.

One specific failure, that we found to be common in our deployment, is when one of the "externals" filesystems report files as missing. This results in Kive job crashing with:

========
Internal Kive Error
========
BlockingIOError: [Errno 11] Resource temporarily unavailable: '/path/to/fastq.gz'

To solve this, we can implement a retry logic.
Whenever there is an error caused by external hardware, pause for some time, and repeat the action again.

We can take inspiration from MiCall that already implements this.

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