You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then when I add sleep(2); inside of my app:test-slack I receive one again.
That means that lock only works until the other server is still running the command. That is potentially dangerous. The issue is, that some tasks can be very quick. Some servers might be delayed with triggering cron ( for example when the cache is not warmed )
Fix:
Lock should probably be for a minute and with a minimal timeout of 60 seconds. Not sure how it works from the symfony lock perspective. Don't think there's ready made mechanism and all implementations I can think of are a bit sketchy. Happy to implement though if pointed in right direction.
The text was updated successfully, but these errors were encountered:
I am not sure if i am not doing something stupid.
Seems that single server only works correctly if the commands are triggered at exactly the same time and are long enough.
Example
I run script:
everything fine
Then I do bash:
I receive two Slack messages
Then when I add sleep(2); inside of my app:test-slack I receive one again.
That means that lock only works until the other server is still running the command. That is potentially dangerous. The issue is, that some tasks can be very quick. Some servers might be delayed with triggering cron ( for example when the cache is not warmed )
Fix:
Lock should probably be for a minute and with a minimal timeout of 60 seconds. Not sure how it works from the symfony lock perspective. Don't think there's ready made mechanism and all implementations I can think of are a bit sketchy. Happy to implement though if pointed in right direction.
The text was updated successfully, but these errors were encountered: