[8.x] add schedule:clear-mutex
command
#40135
Merged
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.
Currently there is no way to clear the mutex files created when using withoutOverlap(). The only way to clear them is using
php artisan cache:clear
however this is dangerous since it clears all other cache as well.If your server restarts while a task is running, the mutex file does not get deleted. Then when the server comes up, it could take up to 24 hours (default value) for your task to re-run because the mutex file still exists. The only way currently to solve this is just running
cache:clear
however this is not optimal.In order to delete only mutex files I added a
schedule:clear-mutex
command.