-
Notifications
You must be signed in to change notification settings - Fork 59
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
Key constraint issues, retry / lookup queries forfailed job #4033
Comments
The interval for each subsequent run is 1 minute: Stracing the scheduler I see the following: A call to Octopoes:
and its results:
Followed by an SQL resultset followed by a call to bytes: Followed by a json result:
|
Please add
bug
, the name of any relevant modules (e.g.rocky
), and any other relevant labels to your issue.Describe the bug
I'm seeing the following logs on postgres:
This is followed up by a read from Octopoes for that specific OOI every few seconds.
And from bytes:
The boefje log indicated an initial upload to Bytes for the raw file was sucesfull, but it tried again and then failed. It then also failed to path the status to "failed".
Grepped for the UUID:
Bytes logs seem to concur when grepping for the UUID:
Expected behavior
I'd expect the retries to stop at some point. But most of all, I'd expect the task to try saving its data only once. (perhaps the task was executed twice due to a race condition somehow?
OpenKAT version
Main
The text was updated successfully, but these errors were encountered: