Queue error logging
Jamroom Developers
brian:
The queue will never just "hang" - that's not how it works or what it does. Again if a queue entry seems to be "stuck" it is a worker issue - it always is. The core queue functions themselves only check to see that a queue has not been held on to by a single worker for longer than you have it configured for, or that it has failed 3 consecutive tries - that's it - it does not do any other checking.
Natedogg265:
I understand I can log an error inside my queue functions. What his complaint is, is that the queue just hangs and we have to manually delete it.
I understand I can log an error inside my queue functions. What his complaint is, is that the queue just hangs and we have to manually delete it.
The queue will never just "hang" - that's not how it works or what it does. Again if a queue entry seems to be "stuck" it is a worker issue - it always is. The core queue functions themselves only check to see that a queue has not been held on to by a single worker for longer than you have it configured for, or that it has failed 3 consecutive tries - that's it - it does not do any other checking.
Forget about the queue. Again, after the conversion function has failed 3 consecutive times, we have not idea why.
We don't know why it failed, what users, what media.
So the a queue log entry telling me something has failed is useless. It does not help us identify and fix the probelem. So a user can potentially be re-submitting a failing job countless times and we can't identify it or fix it.
There are many thing that can cause the function to fail: unable to read/write, corrupt files, invalid formats, etc....
