Skip to content

droplet: only allow configuration maximum concurrent jobs of 0 or 1#465

Merged
franku merged 2 commits intomasterfrom
dev/franku/master/sd-droplet-exit-if-max_concurrent_jobs-gt-1
Mar 31, 2020
Merged

droplet: only allow configuration maximum concurrent jobs of 0 or 1#465
franku merged 2 commits intomasterfrom
dev/franku/master/sd-droplet-exit-if-max_concurrent_jobs-gt-1

Conversation

@franku
Copy link
Contributor

@franku franku commented Mar 27, 2020

There is a known bug when using Storage Backend Droplet with multiple simultaneous jobs (interleaving).
This workaround only allows settings of 0 or 1.
If the default is used (0), it will be set automatically to 1.
If any other value is specified, the bareos-sd will not start at all.

Check droplet devices immediately after configparser-run

There is a known bug when using Storage Backend Droplet with multiple simultaneous jobs (interleaving).
This workaround only allows settings of 0 or 1.
If the default is used (0), it will be set automatically to 1.
If any other value is specified, the bareos-sd will not start at all.

Check droplet devices immediately after configparser-run
@franku franku force-pushed the dev/franku/master/sd-droplet-exit-if-max_concurrent_jobs-gt-1 branch from 010147e to f45892b Compare March 27, 2020 08:01
@franku franku merged commit 238dc53 into master Mar 31, 2020
@franku franku deleted the dev/franku/master/sd-droplet-exit-if-max_concurrent_jobs-gt-1 branch March 31, 2020 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants