Database Queue - the simplest queue, even for shared hosting

IanM

1.1.0

feat: allow configuration of key parameters for the queue blomstra/flarum-ext-database-queue5 as requested by ctml

MikeLundahl

IanM Hi, I'm a little confused. You mentioned that no cron is required anymore. But the documents still say:

Set up

Go into your hosting control panel and set up the following task to run every minute:

php flarum schedule:run
Or in cron language:

* * * * cd /path/to/flarum && php flarum schedule:run

Is it the documents/readme that haven't been updated? Just want to make sure things are setup correctly. (I just updated flarum and its extensions).

GreXXL

MikeLundahl no before that, there was a separate cron job just for DB queues - it's integrated with the scheduler job. This is still required!

xasharma

luceos

GreXXL

Can we use it with https://discuss.flarum.org/d/21873 ?

MikeLundahl

GreXXL Thanks!

GreXXL

xasharma Redis is a different implementation of queues. It's either use Redis or DB queues.

xasharma

GreXXL ok ... Btw which one is better ?

luceos

xasharma

luceos What is the difference with blomstra/flarum-redis?
The redis package (it's officially not an extension) is meant for larger communities. Redis offers the ability to scale the number of workers up however you need. Running a queue worker which pulls jobs from the database can also negatively impact your community performance when processing a lot of notifications and other queue tasks.

xasharma

luceos Great ... Understood.

peopleinside

Today I entered in the Flarum admin where in the Dashboard I see 12 failed job.
This are reported same in two communities.
How to know what this failed job are?

luceos

peopleinside I don't think there's an interface for that yet. But you can find it in the database under failed_tasks I think.

peopleinside

luceos thanks.
flmaqueue_failed_jobs

I found the records and those seems to be old by February 2024 so maybe... the plugin queue still showing me old things already resolved. I will delete this from the database.

A UI for that will be useful and also a way to clean errors 🙂

93ben

I don't know what is happening but every action (no matter if it's updating, installing or removing/deleting extensions) I try to do results in giving this error...

Cause
Unknown
Composer Command
$ composer
Output
Flarum\ExtensionManager\Job\ComposerCommandJob has been attempted too many times or run too long. The job may have previously timed out.

I have cron set up right as it's been sending me emails with the info of the jobs but for whatever reason the script can't successfully add the extension.

BrodyStone21

luceos Go into your hosting control panel and set up the following task to run every minute:

What does this mean? Like in the administration section, or my web server control panel? I don't understand what exactly I'm supposed to do here.

Also, when would you say a community becomes a "large" community? Ie, when should I switch from DB to Redis queue?

EDIT: Nevermind, I set up a cron job. I don't know how to test that it's working though, is there a way?

Also, what are the best settings for the extension itself?

BrodyStone21

@luceos I'm having issues and I don't know what's causing them. I presume my cron job isn't running correctly or something. It keeps showing inactive and jobs don't move from pending.

Running php flarum schedule:run works to resolve it, and it shows "active" on the dashboard, but obviously manually running it kind of defeats the purpose.

Here is the cron job I have set up in cPanel.

And here it is with crontab -e

ernestdefoe

BrodyStone21 change the 1 to a * and see what happens.

luceos

ernestdefoe good catch, the scheduler needs to run every minute using 5 *. Using 1 will only make it run at 1 minute past each hour.

BrodyStone21

ernestdefoe

That's what I had previously, as I had actually set up using crontab -e, but the same issue occured, so I deleted it, and set it up with cPanel. cPanel had no way to use * for the minute, unless I'm missing something?

It appears to be working now. Which leads me to believe I had only included four * and not five.

I'm going to let it run for a while, and I'll let you know if I have any issues.

BrodyStone21

It has unfortunately occurred again. When I check the admin panel throughout the day, I can see pending jobs that never actually move to active, the scheduler still says active, but the status of the queue stays at inactive until I manually run php flarum scheduled:run.

Do you guys have any ideas? Is this going to prevent new users from signing up?

BrodyStone21

BrodyStone21 @luceos idk if you get notifications unless I directly mention you, but do you have any ideas on how to resolve this? Every morning when I go to check, there are pending jobs, and the status is inactive.

Also, can I clear failed jobs, or retry them somehow?

luceos

BrodyStone21 ping me on discord dm please. I'd love see this fixed for you, but this back and forth is taking time I currently am not in excess of.

« Previous Page