Multiple Job Queues

DenSter

Do I understand correctly that multiple instances of NAS can run with startup parameter JOBQUEUE, and it figures out which job needs to be run as part of the process? Is the Job Queue is designed to scale by simply using multiple instances of NAS with the same startup parameter?

ara3n

Based on the way the code is written and that it locks and changes the status of the job queue entry code to in process that yes you can have mulitple NAS instance runnign with same parameter and they will not lock each other out, provided the processes that run do not depend and lock each other out.

Buying a separate NAS is expensive compared to using webservice. 200 for 1 webservice, compared to 4K per NAS.
You would have to do exe upgrade if you are not on 2009.

DenSter

Cool, just what I wanted to hear. We're upgrading a customer to 2009, and they have a customization to the 4.0 Job Scheduler. The modification allows them to set up jobs for a particular instance of NAS (based on the startup parameter it pick up only certain jobs), and kind of manage load balancing that way. With Job Queue having that logic inherently, we can simply put two NAS instances in there with JOBQUEUE, and they will both simply pick up the next job in the queue.

Moving toward web services is out of scope for the moment.

ara3n

It's not a lot of work.


http://mibuso.com/blogs/ara3n/2009/01/2 ... companies/

ara3n

Also make sure you get this hotfix.

https://mbs.microsoft.com/knowledgebase ... -US;948302

DenSter

Thanks