On 10/03/11 08:38, Piotr Lemiesz wrote:
> Hi,
>
> I have about 30 jobs scheduled at 00:00 at priority 10
> I have 1 job scheduled at 02:00 at priority 9
>
> Maximum Concurrent Jobs = 3
> Allow Mixed Priority = yes (in JobDefs)
>
> My intention was to get this "priority 9 job" as close as it is
> possible to 02:00.
> But with my recent configuration it start as a last job.
>
> I thought that the use of "Allow Mixed Priority" somehow pushes this
> "priority 9 job" right after ending one of "priority 10 job" (which
> ended after 02:00), but I was wrong.
>
> Is it possible to set somehow this "priority 9 job" to run close to 02:00 ?
By the sound of things, not without increasing your job concurrency. If
you're starting 30 jobs at 00:00, and allowing only 3 of them to run at
once, then they will have to complete in roughly 12 minutes each if you
want your scheduled 02:00 job to be able to start on time.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
