View Issue Details

IDProjectCategoryView StatusLast Update
0001063bareos-core[All Projects] Generalpublic2019-09-25 01:24
Reportercm@p-i-u.deAssigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status newResolutionopen 
PlatformLinuxOSCentOSOS Version7
Product Version18.2.5 
Target VersionFixed in Version 
Summary0001063: Add option to set priority to schedule Resource
DescriptionCurrently it is still not possible to schedule a weeky and monthly based Pool Backup on fridays, because it happens that 2 Jobs overlap each other having a schedule like this
(Some month have 5 fridays others only 4 fridays)

Schedule {
  Name = "Default"
  Run = pool=Daily mon-thu at 22:30
  Run = pool=Weekly 1st-4th fri at 22:30
  Run = pool=Monthly last fri at 22:30
}

To solve this isssue it would be great to have priority keyword added to the scheduler similar like in the job resource. With this option it is possible to define which job should take precedence if more then one job match the scheduler criteria.

For example like this,
run Weekly but have Monthy take precedence if both would match

Schedule {
  Name = "Default"
  Run = pool=Daily mon-thu at 22:30
  Run = pool=Weekly 1st-4th fri at 22:30 priority = 20
  Run = pool=Monthly last fri at 22:30 priority = 10
}
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

arogge

arogge

2019-07-12 10:57

developer   ~0003450

you can work around this by scheduling monthly five minutes early and disallowing duplicate jobs.
While I think you're right that we need something like "every friday, but the last", I would assume that priority in this context would override the job's priority (like pool and level do) and not declare the priority of this schedule entry.

Can you update your proposal so we don't have this kind of ambiguity?
cm@p-i-u.de

cm@p-i-u.de

2019-09-23 22:19

reporter   ~0003580

The problem with the workaround is, that than one job is marked as canceled this is confusing the enduser (which is in our SME scenario is set up to control backups via webui).
Explaining to the user that the job marked as canceled (failed) but it isn't, is not leading into the right directions how to handle failed jobs.

Regarding priority I meant, that the schedule itselfs has priorities but not in the sense like priorities are handled on jobs but in the way that a schedule with a higher priority overrides the lower priority ones.
For example having 5 schedules, scheduled at the same point in time, the one with highest priority wins.
arogge

arogge

2019-09-24 09:04

developer   ~0003581

I totally understand you request and the drawbacks of the automatic cancelling.

The main problem I have right now is, that the configuration syntax your propose is ambigous and misleading.
If you can come up with something that isn't misleading, we might consider to put this on the agenda.
cm@p-i-u.de

cm@p-i-u.de

2019-09-25 01:19

reporter   ~0003582

Than maybe the best thing is to find another verb instead of priority, because with the implementation shown above there are really a lot things possible where more than one condition applies.

For example (a litte bit overdriven but just to illustrate it clearly) you schedule a job on the 30th of the month, which may also be the last day in the month and allso a friday, having schedules for fridays, last day of the month in additiion to the schedule for 30th of the month, you could control which one should take precedence.

Maybe "precendence" is also the word to be used :-)
cm@p-i-u.de

cm@p-i-u.de

2019-09-25 01:24

reporter   ~0003583

"rank" comes also to mind

Issue History

Date Modified Username Field Change
2019-02-22 23:49 cm@p-i-u.de New Issue
2019-07-12 10:57 arogge Status new => feedback
2019-07-12 10:57 arogge Note Added: 0003450
2019-09-23 22:19 cm@p-i-u.de Note Added: 0003580
2019-09-23 22:19 cm@p-i-u.de Status feedback => new
2019-09-24 09:04 arogge Note Added: 0003581
2019-09-25 01:19 cm@p-i-u.de Note Added: 0003582
2019-09-25 01:24 cm@p-i-u.de Note Added: 0003583