Hi,
I'm using horizon for my jobs. When I run a shell command in my job:
exec(env('FFMPEG_PATH').' -i '.$this->file. ' '.$newFileFullPath);
And have horizon running in the background php artisan horizon. I see that the script is executed (i can see it's running for a long time, it's converting a file). However, why am even seeing this? I would only expect to see that a job has dispatched and is running. For example: Processed: App\Jobs\CampaignFileUploadJob . It looks like my exec() command is blocking all other jobs that are dispatched.
Any idea if this is normal and how I can fix this?
queue jobs are run in a row
if you want jobs running in //, use sevral workers.
if you don't want to wait the result of your exec, follow this link
https://stackoverflow.com/questions/3819398/php-exec-command-or-similar-to-not-wait-for-result
@sr57 I wouldn't suggest running this in the background, then what is the point of having a queued job?
@bugsysha It's my second option and we dont' know the usage ...
@sr57 yes, I understand that. Just wanted to highlight it to the OP so it is clear it is a sub-optimal solution.
It looks like my exec() command is blocking all other jobs that are dispatched.
That is not what is happening. You've probably configured to run only one job at a time.
@bugsysha hmm so it's not a bad thing? Is it normal to do it like this if you want to run jobs in sequence?
@Lars-Janssen I would suggest either dispatching the next job from the current job or using batch jobs or just job chains depending on what you need. Everything is in the docs so I encourage you to read it.
https://laravel.com/docs/9.x/queues
so it's not a bad thing?
It should be considered a bad thing because you have a bottleneck. But it depends on what you need. If this is your own app that will only be used by you and you will never have needs for greater throughput, then you can leave it. In all other cases, I would suggest doing it properly.
Please or to participate in this conversation.