-
Notifications
You must be signed in to change notification settings - Fork 190
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
It makes unexpected pauses #350
Comments
@dima4p Please provide more context. What do you mean by 'runner'? What does a log message mean? What is your worker configuration? What does the worker/database CPU usage look like? What kind of work is the job doing? Are there particular job options in use? |
An instance of que. In my case:
In the first pairs of [] there is time and PID. You can see, that during the execution of the task there is a message about every 4 seconds. At the end of every job execution there is a message with the string "Line@125".
I think the answer is above.
Until 18:13:33 the load was high, about 80% on every core. But between 18:13:33 and 18:30:48 very low.
The job reads a file, parses it to recognise a time and for each line created a record in the DB with the parsed time.
Only id of the record pointing on the file to read. |
I forgot to mention, that during the pause the queue of the jobs was long. |
I'm afraid I can't think of a reason for this. Perhaps |
@dima4p how large are the files you are reading? Is it possible there is a db lock somewhere within your transaction that blocks other workers? I can’t help but notice that the first log message after the gap for every single worker process is: |
I'm currently looking at a similar issue. There's one job class queued multiple times (with different arguments) as multiple jobs. And although there are 6 worker threads, que only processes one of these jobs. I can see that the Unfortunately there isn't any log output either. Even though the full command line says
(I added the last one as a |
@milgner If you've set I still can't work out how to reproduce this. Again, a minimal Que app demonstrating this behaviour would be very helpful. |
I have met the same problem in other project. In the console I see there is one job ready to be executed:
I bit earlier I have restarted
In the log there is:
and then the messages are repeated. Since nothing happened, I restarted as usual:
The job remains waiting… The only thing that helps is deleting the job and creating a new one. the version of |
There are active runners and active jobs, but for a while none is in work.
Here is the log, where the pause is clear seen
What can be the reason for this delay?
The text was updated successfully, but these errors were encountered: