[mythtv-users] Transcode jobs execute on the backend in which the video was recorded?
klein.aaron at gmail.com
Sun Aug 10 19:11:35 UTC 2008
Im aware of that setting and have it checked on both backends. Yet
even today I scheduled three transcoding jobs from mythweb and the
first started on the primary backend where all three programs where
recorded and the other two errored because the secondary backend tried
to transcode them.
On Sat, Aug 9, 2008 at 9:54 PM, Brad DerManouelian
<myth at dermanouelian.com> wrote:
> On Aug 9, 2008, at 3:25 PM, Aaron Klein wrote:
>> I have two backends in a master and slave situation. I am seeing job
>> load balencing on tasks like commflag and transcode. For commflag
>> this load balencing causes the backend that is not recording the show
>> to do the commflaging. So if backend 1 is recording usually backend 2
>> does the commflagging. Or if I schedule a transcode job to occur on
>> backend 1 for a show that was recorded on backend 1 it will
>> occasionally run on backend 2 expecially if backend 1 is already
>> running a job like a transcode or commflag. This of course causes
>> problems if one schedules a series of transcode jobs in a row to
>> execute one right after the other.
>> How can I configure these systems to only run the transcode job on the
>> backend in which the show was acutally recorded on.
> Check the box that says, "Run Jobs only on original recording backend".
> It's the second Job Queue page in the General Options in mythtv-setup.
> mythtv-users mailing list
> mythtv-users at mythtv.org
More information about the mythtv-users