Menu
▾
▴
[Bacula-bugs] [bacula 0001709]: Max concurrent jobs for changer takes no notice of Tape drive concurrency settings
|
From: Mantis B. T. <no...@bu...> - 2011-03-21 14:44:32
|
Issue 0001709 is now monitored by user mnalis. ====================================================================== http://bugs.bacula.org/view.php?id=1709 ====================================================================== Reported By: stoatwblr Assigned To: ====================================================================== Project: bacula Issue ID: 1709 Category: Storage Daemon Reproducibility: always Severity: major Priority: high Status: new ====================================================================== Date Submitted: 2011-03-17 11:40 GMT Last Modified: 2011-03-21 14:44 GMT ====================================================================== Summary: Max concurrent jobs for changer takes no notice of Tape drive concurrency settings Description: According to Kern, "Maximum Concurrent Jobs" for a device is supposed to be respected, even if part of an autochanger. This is not occurring. If a job uses an autochanger, then all concurrency settings for the component drives are ignored in favour of the autochanger concurrency setting. This can lead to many jobs running on one device in an autochanger while other devices are idle. Steps to Reproduce: Create an autochanger storage entry with 2 or more component drives. Set Maximum Concurrent Jobs=10 for the autochanger Set Maximum Concurrent Jobs=2 for the drives Start multiple jobs which will use the same drive (same pool). The number of jobs running on any given drive will go up to 10, not the configured limit of 2. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2011-03-17 11:40 stoatwblr New Issue 2011-03-21 14:44 mnalis Issue Monitored: mnalis ====================================================================== |