Commit 3ebed1a1 authored by Klaus Aehlig's avatar Klaus Aehlig
Browse files

Describe the new scheduling parameter in NEWS



We have added a new scheduling feature, so describe it in NEWS.
By default, it has no effect (the default for --max-tracked-jobs
is higher than the default of --max-running-jobs), but it explains
how luxid will keep reactive if --max-running-jobs is increased.
Signed-off-by: default avatarKlaus Aehlig <aehlig@google.com>
Reviewed-by: default avatarPetr Pudlak <pudlak@google.com>
parent b1365e8f
......@@ -40,6 +40,13 @@ New features
manage and supervise all Ganeti processes.
- Different types of compression can be applied during instance moves, including
user-specified ones.
- Ganeti jobs now run as separate processes. A consequence is that more jobs can
run in parallel; the number is run-time configurable, see "New features" entry
of 2.11.0. To avoid luxid being overloaded with tracking running jobs, it
backs of and only occasionally, in a sequential way, checks if jobs have
finished and schedules new ones. In this way, luxid keeps responsive under
high cluster load. The limit as when to start backing of is also run-time
configurable.
Version 2.11.2
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment