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 lock ttl configurable #23553

Merged
merged 1 commit into from
Apr 8, 2016
Merged

Make lock ttl configurable #23553

merged 1 commit into from
Apr 8, 2016

Conversation

icewind1991
Copy link
Contributor

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

@icewind1991 icewind1991 added this to the 9.1-current milestone Mar 24, 2016
@icewind1991 icewind1991 mentioned this pull request Mar 24, 2016
@DeepDiver1975
Copy link
Member

@icewind1991 there is something totally broken with the unit test execution - setting back to developing

@icewind1991
Copy link
Contributor Author

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.
Copy link
Contributor

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 ?

Copy link
Contributor Author

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fix the wording issue

@icewind1991 icewind1991 force-pushed the lock-ttl-execution-time branch from 792598b to 23bcf78 Compare March 24, 2016 14:26
@PVince81
Copy link
Contributor

Looks fine, both db locking and redis locking still seem to work 👍

@rullzer
Copy link
Contributor

rullzer commented Mar 30, 2016

👍

@rullzer rullzer force-pushed the lock-ttl-execution-time branch from 23bcf78 to cdedda9 Compare April 7, 2016 06:28
@DeepDiver1975 DeepDiver1975 merged commit 1d3d43b into master Apr 8, 2016
@DeepDiver1975 DeepDiver1975 deleted the lock-ttl-execution-time branch April 8, 2016 12:53
@lock
Copy link

lock bot commented Aug 6, 2019

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.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

File Is Loked
4 participants