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

Make sure that tasks do not replicate themselves #1307

Open
sveneberth opened this issue Oct 29, 2024 · 0 comments
Open

Make sure that tasks do not replicate themselves #1307

sveneberth opened this issue Oct 29, 2024 · 0 comments
Assignees
Labels
bug(fix) Something isn't working or address a specific issue or vulnerability Priority: High After critical issues are fixed, these should be dealt with before any further issues.

Comments

@sveneberth
Copy link
Member

I think the problem has existed since ViUR 2 ...

I experience it more and more often that with long tasks (many chunks, over hours / days), the task is duplicated and executed several times in parallel. On the one hand, this naturally leads to more resources being consumed, on the other hand it leads to transaction collisions.

This can actually only happen if an error occurs between the call of the next chunk and the completion of the task (network error, timeout), so that the next chunk is queued but the last chunk is evaluated as failed.

Some mechanism is needed here that recognizes that a task is already one execution further.

@sveneberth sveneberth added bug(fix) Something isn't working or address a specific issue or vulnerability Priority: High After critical issues are fixed, these should be dealt with before any further issues. labels Oct 29, 2024
@sveneberth sveneberth self-assigned this Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug(fix) Something isn't working or address a specific issue or vulnerability Priority: High After critical issues are fixed, these should be dealt with before any further issues.
Projects
None yet
Development

No branches or pull requests

1 participant