Status: New
Owner: ----
New issue 741 by [email protected]: gnt-job not always running the
job with highest priority
http://code.google.com/p/ganeti/issues/detail?id=741
Please provide any additional information below.
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
What distribution are you using?
root@node1 ~ # gnt-cluster --version
gnt-cluster (ganeti v2.9.4) 2.9.4
root@node1 ~ # gnt-cluster version
Software version: 2.9.4
Internode protocol: 2090000
Configuration format: 2090000
OS api version: 20
Export interface: 0
VCS version: v2.9.4
root@node1 ~ # hspace --version
hspace (ganeti) version v2.9.4
compiled with ghc 7.4
running on linux x86_64
root@node1 ~ # cat /etc/debian_version
7.4
root@node1 ~ # dpkg -l ganeti
ii ganeti 2.9.4-1~bpo70+1
What steps will reproduce the problem?
1. gnt-instance replace-disks --submit --priority=low -s ns
2. gnt-instance replace-disks --submit --priority=low -s ns2
3. gnt-instance replace-disks --submit --priority=normal -s ...
4. gnt-instance replace-disks --submit --priority=low -s ...
5. gnt-[...]
6. gnt-cluster modify -D drbd:resync-rate=$((96*1024)) --priority=high
--submit
What is the expected output? What do you see instead?
high to be run first / next
< often picking of high, but not always
Please provide any additional information below.
ID Priority Status Summary
70386 7 waiting INSTANCE_REPLACE_DISKS(mail.example.de)
70387 7 waiting INSTANCE_REPLACE_DISKS(web.example.de)
70389 -3 waiting CLUSTER_VERIFY_CONFIG
70390 0 waiting
CLUSTER_VERIFY_GROUP(945dead6-019c-4b8b-a4fd-7081d9aa683b)
70391 8 waiting INSTANCE_REPLACE_DISKS(vm01.example.de)
70392 9 waiting INSTANCE_REPLACE_DISKS(vm02.example.de)
70393 -10 running INSTANCE_REPLACE_DISKS(vm03.example.de)
70394 -3 waiting QUERY(instance),QUERY(node)
70395 7 waiting INSTANCE_REPLACE_DISKS(vm04.example.de)
70397 7 waiting INSTANCE_REPLACE_DISKS(vm05.example.de)
70398 7 waiting INSTANCE_REPLACE_DISKS(vm06.example.de)
70399 -12 waiting INSTANCE_MIGRATE(ns.example.de)
70400 -12 waiting CLUSTER_SET_PARAMS
// 70393 finished
ID Priority Status Summary
70386 7 waiting INSTANCE_REPLACE_DISKS(mail.example.de)
70387 7 waiting INSTANCE_REPLACE_DISKS(web.example.de)
70389 -3 waiting CLUSTER_VERIFY_CONFIG
70390 0 waiting
CLUSTER_VERIFY_GROUP(945dead6-019c-4b8b-a4fd-7081d9aa683b)
70391 8 waiting INSTANCE_REPLACE_DISKS(vm01.example.de)
70392 9 waiting INSTANCE_REPLACE_DISKS(vm02.example.de)
70394 -3 waiting QUERY(instance),QUERY(node)
70395 7 waiting INSTANCE_REPLACE_DISKS(vm04.example.de)
70397 7 waiting INSTANCE_REPLACE_DISKS(vm05.example.de)
70398 7 waiting INSTANCE_REPLACE_DISKS(vm06.example.de)
70399 -12 running INSTANCE_MIGRATE(ns.example.de)
70400 -12 waiting CLUSTER_SET_PARAMS
// 70399 finished ... continueing with 70387(?) not 70400(!)
ID Priority Status Summary
70386 7 waiting INSTANCE_REPLACE_DISKS(mail.example.de)
70387 7 running INSTANCE_REPLACE_DISKS(web.example.de)
70389 -3 waiting CLUSTER_VERIFY_CONFIG
70390 0 waiting
CLUSTER_VERIFY_GROUP(945dead6-019c-4b8b-a4fd-7081d9aa683b)
70391 8 waiting INSTANCE_REPLACE_DISKS(vm01.example.de)
70392 9 waiting INSTANCE_REPLACE_DISKS(vm02.example.de)
70394 -3 waiting QUERY(instance),QUERY(node)
70395 7 waiting INSTANCE_REPLACE_DISKS(vm04.example.de)
70397 7 waiting INSTANCE_REPLACE_DISKS(vm05.example.de)
70398 7 waiting INSTANCE_REPLACE_DISKS(vm06.example.de)
70400 -12 waiting CLUSTER_SET_PARAMS
// 70400 finished
// 70394 finished
// 70389 finished ... continueing with 70386(?) not 70390(!)
ID Priority Status Summary
70386 7 running INSTANCE_REPLACE_DISKS(mail.example.de)
70390 0 waiting
CLUSTER_VERIFY_GROUP(945dead6-019c-4b8b-a4fd-7081d9aa683b)
70391 8 waiting INSTANCE_REPLACE_DISKS(vm01.example.de)
70392 9 waiting INSTANCE_REPLACE_DISKS(vm02.example.de)
70394 0 waiting QUERY(instance),QUERY(node)
70395 7 waiting INSTANCE_REPLACE_DISKS(vm04.example.de)
70397 7 waiting INSTANCE_REPLACE_DISKS(vm05.example.de)
70398 7 waiting INSTANCE_REPLACE_DISKS(vm06.example.de)
// set 70390 to high
ID Priority Status Summary
70386 7 running INSTANCE_REPLACE_DISKS(mail.example.de)
70390 -10 waiting
CLUSTER_VERIFY_GROUP(945dead6-019c-4b8b-a4fd-7081d9aa683b)
70391 8 waiting INSTANCE_REPLACE_DISKS(vm01.example.de)
70392 9 waiting INSTANCE_REPLACE_DISKS(vm02.example.de)
70395 7 waiting INSTANCE_REPLACE_DISKS(vm04.example.de)
70397 7 waiting INSTANCE_REPLACE_DISKS(vm05.example.de)
70398 7 waiting INSTANCE_REPLACE_DISKS(vm06.example.de)
70401 0 waiting
GROUP_VERIFY_DISKS(945dead6-019c-4b8b-a4fd-7081d9aa683b)
// 70386 finished ... coninueing with 70397(?) not 70390(1)
ID Priority Status Summary
70390 -10 waiting
CLUSTER_VERIFY_GROUP(945dead6-019c-4b8b-a4fd-7081d9aa683b)
70391 8 waiting INSTANCE_REPLACE_DISKS(vm01.example.de)
70392 9 waiting INSTANCE_REPLACE_DISKS(vm02.example.de)
70395 7 waiting INSTANCE_REPLACE_DISKS(vm04.example.de)
70397 7 running INSTANCE_REPLACE_DISKS(vm05.example.de)
70398 7 waiting INSTANCE_REPLACE_DISKS(vm06.example.de)
70401 0 waiting
GROUP_VERIFY_DISKS(945dead6-019c-4b8b-a4fd-7081d9aa683b)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
