Queue depth status
Using Jamroom
Hi Brian,
Just wanted to check in and see if you figured out the issue with the 404 error. It's a blocker for us now.
Forum Activity for @dannya
Queue depth status
Using Jamroom
That does. Thanks. (I don't know how you managed to get the answers out before I even hit send!)
Queue depth status
Using Jamroom
Sounds promising. A couple of questions:
1. Can different types of encoding jobs have different priorities? Or Is it just by job TYPE.
2. Is there a reason you went with just high/low vs a numerical value? It seems a numerical value would give you much more control.
3. When is this release expected?
FYI, the use case for the queue status is for managing queues as well. I am trying to use the queue status to autoscale a cluster of conversion servers OR send overflow to AWS elastic transcoder if the queue length gets too long. It seems like a conversion server can only process a few jobs concurrently (depending on memory and number of cpu cores), so if more than a couple of users are uploading at a time, the queue can really get backed up quickly.
updated by @dannya: 07/10/16 09:57:20AM
Queue depth status
Using Jamroom
Email is was not a big of a deal for me, but now that you mention it I think it became much more relevent.
My use case was more for encoding priority. I encode to multiple formats; however only one is needed before the file is available to the player. I wanted to make sure that one gets processed right away so the user is not waiting.
I didn't think email was an issue, because I wasn't using the conversion server to send emails. But now that you mention it, I didn't realize emails were getting held up by conversions. I thought the email would get picked up by the email server regardless of the conversion jobs in the queue. I hope that is the case and maybe you can confirm.
If that's still true, one approach to prioritization is to dedicate servers to certain types of queue jobs; so that they don't get held up by conversions. However, I'd still like to assign a priority to the conversions.
Queue depth status
Using Jamroom
Ok. Thanks. Just saw the other one too. I was hoping Pauls answer was not definitive. May have to do something custom unless you have any plans to do something. It would be great to set a PRIORITY parameter on a job and have the client execute the highest priority job first.
updated by @dannya: 07/09/16 04:28:29PM
Queue depth status
Using Jamroom
To be clear cloud queue server is working, but we are still getting the error for the get active queue info function. Also still hoping for answer for other thread about queue prioritization.
Queue depth status
Using Jamroom
Yes. Cloud core is configured. The queue server is otherwise working and doling out tasks to conversion servers.
Queue depth status
Using Jamroom
Error now 404 instead of 400
Array
(
[code] => 404
[text] => Not Found
)
Queue depth status
Using Jamroom
Using this, we are getting the following error
Array
(
[code] => 400
[text] => Bad Request
[note] => invalid payload
)
