BackgroundTasks: Use "Fire & Forget" approach when starting workers as… #8147
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mjansenDatabay
changed the title
mjansenDatabay
force-pushed
the
improvement/10/bgtasks-async-fireforget
branch
from
dc5af8c
to
2d3776a
Compare
|
Thanks a lot! I seen no problem to merge this in trunk, but maybe this could be helpful in 8-9 as well. do you have any experience with this in productive releases? |
Hi @chfsx , thanks for the question: We use this in an ILIAS 6.x installation (productive system) where this solves issues with a high usage of async. background tasks, each handling complex "Learning Progress Re-calculations". Best regards |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ynchronously
This PR suggests making the start of asynchronous workers for background tasks really asynchronous to ensure a "Fire & Forget" approach. This is done by setting the "Response Timeout" to
0and by adding aignore_user_abort(true);) on the server-side (SOAP).