[mythtv-users] Backend not honoring "MaxSimultaneousJobs"

Jon jtlarson at u.washington.edu
Tue Sep 25 17:26:53 UTC 2007

On Tue, 2007-09-25 at 10:47 -0400, Chris Pinkham wrote:
> * On Tue Sep 25, 2007 at 06:47:46AM -0700, Jon Larson wrote:
> > >select *
> > >	from jobqueue
> > >	where value in ( 'JobsRunOnRecordHost', 
> > >	'JobQueueMaxSimultaneousJobs');
> > >
> > >Both of those are global settings, so there should only be one row
> > >for each setting and the hostname should be NULL on those rows.
> > Thanks Chris--'JobsRunOnRecordHost' is set correctly; however I can see 
> > that there are 3 'JobQueueMaxSimultaneousJobs'--each one bears the 
> > hostname of one of the servers--so that's  probably the problem. I am at 
> Sorry, I don't know what I was thinking when I typed that.  The max jobs
> is a per-host setting, so there should be one row per host and no NULL
> host entry.

I didn't see your response until after I had deleted the host-specific
entries and replaced them with a global entry. 

> What do you see in the backend and frontend logs when you run both with
> "-v database".  That will show you all SQL queries.  Grep out the ones for
> the jobqueue table and see what values are being put in the table.

The funny thing is that after making the changes above, it seems to be
working. I started 3 jobs and they were split between 2 servers without
incident. I then saw your message and started a 4th with the -v database
option on the frontend:

2007-09-25 09:56:45.365 MSqlQuery: INSERT INTO jobqueue (chanid,
starttime, inserttime, type, status, statustime, hostname, args,
comment, flags) VALUES ('1005', '2007-09-24T13:29:00', now(), 256, 1,
now(), '', '', '', 0);

The backends are busy right now so I'll have to wait to re-run them with
-v database. My question is, should I re-add the host-specific
'JobQueueMaxSimultaneousJobs' entries or is it ok to leave as is?


More information about the mythtv-users mailing list