You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: