-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recurring schedule after an hour did not work anymore #445
Comments
Hey @lrjbrual, sorry for the delay! It's odd that the job stops being scheduled. When this happens, can you check which processes are running in the server where you're running
|
Hi @rosa, No, problem. Appreciate your reply. I am using DigitalOcean App platform, using web resource without worker. here are the log information:
After I revalidate again:
It skipping the schedule of 19:50 and for sure the same again: |
Huh, what did it happen between this
and this?
As there, solid queue is no longer running so that's the reason the job is not being enqueued, but any ideas of what happened? |
That is what I am looking for, why it is happening. I added honeybadger to revalidate. it seems after 3 times attempt it clear up the solid queue, cannot find what is going on, yet. @rosa, do you also know how to clean up some continuous connections to the database? for example instead of creating a new connection it will re-use the old connection. and I found it connects multiple times, and I have limited the database connection to 22. I'm not sure how to deal with clean up the connection or re-use it; I'm still exploring the solid queue documentation. I will continue to to monitor until tomorrow if I have still an issue with running a solid queue. I rerun again the bin/jobs start and it is almost 2 and hop hours and still running; I Hope it will continue without issues. |
Hey @lrjbrual, so sorry for the delay replying! Somehow I missed the notification for your last comment 🤦♀️ You don't need to manually clean up any DB connection, Solid Queue relies on Active Record for that.
Where do you have limited this? In Rails's |
Hi,
We have current setup in DigitalOcean to run an API to send data to another third party app. and it success processing the jobs during 1 to 2 hours, We are using DigitalOcean App platform container.
Here is our setup of recurring.yml
However after one hour to two hours the jobs does not work anymore:
here is the screenshot:
the finished job, after there is no:
Here is pick high memory use:
Our logs.
in Addition, when using also puma, to add: bin/jobs start
I am not sure what is going on, why the jobs stop. or do we need to add a worker? But on the other app, we are using a good job,. We are using web only in DigitalOcean, not with worker, but it seems to be working, and it is a heavy load of APIs.
Thanks you in advance for assistance and help.
The text was updated successfully, but these errors were encountered: