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
New Feature: onOneServer #42
Comments
Hello, blocking store is not required, it was fixed in docs and code do not acquire blocking locks. Did you test |
Unfortunately I didn't mention it, I refer to 3.4 but in 3.5 it is still the same The check for BlockingStoreInterface is still there, if I understand it correctly. Lines 721 to 732 in 9148a14
And yes, I tried it with PDO Store |
Yes, but
Does it work? |
No, at least in v3.4 (PHP 7.4) there is no
|
Which Symfony Lock version? |
|
OK, looks like bug in Crunz, will be fixed soon. |
@gennadiylitvinyuk please try #44 |
Yes, it works this way |
Description
An option to indicate that the task should run on only one server, similar to laravel's onOneServer like described in https://laravel.com/docs/9.x/scheduling#running-tasks-on-one-server
It is not possible to achieve the same results with
preventOverlapping
because the current implementation ofpreventOverlapping
allows passing only locks implementing BlockingStoreInterface. It leads task execution once per server, but not in the same time.The text was updated successfully, but these errors were encountered: