-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 lock ttl configurable #23553
Make lock ttl configurable #23553
Conversation
@icewind1991 there is something totally broken with the unit test execution - setting back to developing |
237b245
to
792598b
Compare
all fixed |
* | ||
* Any lock older than this will be automatically cleaned up. | ||
* | ||
* If not set this defaults the the either 1 hour or the php max_execution_time, whichever is higher. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"the the"
How to unset it to have it be the default ? Set to 0 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How to unset it to have it be the default
Just not set it in the config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix the wording issue
792598b
to
23bcf78
Compare
Looks fine, both db locking and redis locking still seem to work 👍 |
👍 |
23bcf78
to
cdedda9
Compare
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fixes #22591
Makes the lock ttl configurable in
config.php
and changes the default ttl to be either 1 hour or the php max_execution_time, whichever is higher.By using max_execution_time as ttl we make sure we don't run into the issue of removing a lock of a process that's still running.
@Ma1kavian can you verify that this fixes the problem (undo the change to the ttl you made and apply this patch, you shouldn't need to configure the ttl manually since it takes the max_execution_time into account)
cc @PVince81