Hard and soft time out settings
10Aug2012
Posted by hvassing
Hi,
we would like to propose introducing a differentiated sets of time out settings; hard and soft time out.
The soft time out setting would be the length of time a job would be allowed to run without making any progress, before timing out and setting the transcoding status to failed. This setting could be specified in minutes.
The hard time out setting would then be the total length of time a job would be allowed to run, regardless of progress. This is how the time out setting is currently working in MediaMosa. This setting should be specified in hours.
- Login or register to post comments
- Printer-friendly version
- Send by email
Comments
Well, we are planning to
Posted by Robert on August 13th, 2012 - 09:00Well, we are planning to re-write the job server software with v4.0, and this will one of the things you will be able to do. The current version is written around the LHA scripts that handle ffmpeg. In the new version we will get rid of LHA and replace it with normal PHP scripts. That will allow to monitor and kill jobs, which is not completely possible with the current version; all is indirect with LUA. Communication between LHA en MM is done with a status file, which is enough for the what is what designed for. But its no longer enough. If jobs timeout then MediaMosa just assumes the job is finished or is killed. At least with PHP we can put a maximum on the script execution time and let it kill the processes it has started and communicate with MediaMosa with internal REST calls, opening up a lot more and powerful options. Think about real time queue handling, prioritize jobs and give certain apps more priority above others etc.
Hi all, what's the actual
Posted by DZenker on August 14th, 2012 - 09:28Hi all,
what's the actual (and realistic ;-) roadmap of the MediaMosa development?
When will V. 3.5 or 4.0 be released?
Greets,
Dietmar
Because of your question,
Posted by Robert on August 14th, 2012 - 14:18Because of your question, I've updated the roadmap page (was about a year behind, oops);
http://mediamosa.org/content/roadmap
I'm in the middle of finishing, checking, bug squashing of version 3.5. The biggest hold up is the PostgreSQL patch, which has become huge in size. It was a needed patch, as it will fix a number of other issues with MySQL we where having (ACL asset protection is one). Once that patch is done, Ill merge with all the other updates and release a RC1. I just can not pin point a date yet. I just hope its within the next 2 weeks. Release of v3.5 stable is planned before the end of September.
v4.0 is planned for Q1 2013 and has already been in development since last year as we already have completely rewritten the REST software from scratch. More information on this release will come right after v3.5 release.