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
I'm checking the docs about "onOneServer", as I'd like to have more than one server running the scheduler. As far as I've understood, and checked into laravel's code, the servers running the scheduler must have their clocks completely synchronized.
If not, it'd be possible for one server to run a task on minute "6:00", finish one second later, and then have another server run the same task because the clock is one second behind.
May someone help me understand if am I right?
If my above assumption is correct, shouldn't we have a new method to run the tasks "oncePerTime", as having the servers' time synchronized is difficult?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, good morning.
I'm checking the docs about "onOneServer", as I'd like to have more than one server running the scheduler. As far as I've understood, and checked into laravel's code, the servers running the scheduler must have their clocks completely synchronized.
If not, it'd be possible for one server to run a task on minute "6:00", finish one second later, and then have another server run the same task because the clock is one second behind.
May someone help me understand if am I right?
If my above assumption is correct, shouldn't we have a new method to run the tasks "oncePerTime", as having the servers' time synchronized is difficult?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions