Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Cache] disable lock on CLI#44669
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
15f5e09 tob968514Comparestof commentedDec 16, 2021
The issue was talking about problems happening in Apache, so I doubt that disabling it only on CLI will fix it. |
nicolas-grekas commentedDec 16, 2021
It was about apache calling commands in a subprocess, isn't it? |
stof commentedDec 16, 2021
#41130 (comment) should be checked, as it talks about nested caching in parallell requests |
nicolas-grekas commentedDec 16, 2021
Calling |
I thought using semaphores would fix the linked issue but I'm proposing to revert them in#44667
Instead, I think we should disable the lock on CLI processes.
The purpose of having locks enabled by default is to prevent cache stamped at deploy time. Disabling the lock on CLI still provides this protection on eg FPM.
For ppl that really want a lock between eg crons and FPM, the lock component should be used instead.