How does Laravel scheduled task work on different servers?

@Snapey Sorry I don't get you. The link you provided is for running tasks on one server, but I want to run task on multiple servers.

@zhaogood than don't use a central cache for your scheduler

$schedule->useCache('file');

// your scheduled commands

@krisi_gjika Thanks. There are some other tasks do require central cache.

@zhaogood you will have to test this yourself but try to change the cache driver after those commands

@zhaogood

Sorry I don't get you.

Did you even read the section? Its only like two paragraphs

If your application's scheduler is running on multiple servers, you may limit a scheduled job to only execute on a single server. For instance, assume you have a scheduled task that generates a new report every Friday night. If the task scheduler is running on three worker servers, the scheduled task will run on all three servers and generate the report three times. Not good!

To indicate that the task should run on only one server, use the onOneServer method when defining the scheduled task. The first server to obtain the task will secure an atomic lock on the job to prevent other servers from running the same task at the same time:

Its about ENSURING your job only runs on one server (the first one that can run it)

@Snapey I don't want to run a command only on one server. I want to run a command on ALL servers and without overlapping.

@zhaogood again your comment demonstrates you did not read the docs

The first server to obtain the task will secure an atomic lock on the job to prevent other servers from running the same task at the same time:

@Snapey your comment demonstrates you did not read the docs carefully. This is the full paragraph of the sentence you copied from https://laravel.com/docs/10.x/scheduling#running-tasks-on-one-server:

To indicate that the task should run on only one server, use the onOneServer method when defining the scheduled task. The first server to obtain the task will secure an atomic lock on the job to prevent other servers from running the same task at the same time:

I don't know why you didn't read the first sentence. It clearly states this atomic lock is for onOneServer method, which I DON'T use.

I already knew the atomic lock story. Both onOneServer method and withoutOverlapping would create a mutex(atomic lock), but they are different. What I am trying to say is why withoutOverlapping also prevent tasks from different servers. In my opinion withoutOverlapping should only block the overlapping tasks from the same server.

@zhaogood ok, sorry, I did not get the gist of your question and mistook your explanation of what happens as a description of what you want to happen

Short of a PR, you could stagger the schedules by some minutes dependent on something like a server node number.

If your servers were 0,1, & 2 adapt your schedule like

    schedule->command('foo:bar')->hourlyAt($this->atMinutes());

    public function atMinutes()
    {
        $slots = [
            [10,20,30,40,50,0],
            [12,22,32,42,52,2],
            [14,24,34,44,54,4],
        ];

        return $slots[config('app.serverNode')];
    }

@Snapey thank you. The problem is I need to use withoutOverlapping() so the command doesn't run overlap in each server. I mean we don't really know how long the command will take. It could be seconds, or hours.

@zhaogood how about your own local mutex? let your job start and quit if the mutex is still valid