Comment #4 on issue 805 by [email protected]: Do not use job queue for
running individual jobs in separate processes
http://code.google.com/p/ganeti/issues/detail?id=805
Start by removing features of the Python job queue that are no longer
needed.
commit 10e7e07eba2e7fcb2705fe2cae8fe6e203305344
Author: Klaus Aehlig <[email protected]>
Date: Wed Jun 11 16:21:08 2014 +0200
Remove accepting_jobs from jqueue
Given that the Python job queue now only handles a single job,
there is no need to keep track on whether it accepts new jobs.
Hence remove that code. Also remove the corresponding tests.
Signed-off-by: Klaus Aehlig <[email protected]>
Reviewed-by: Petr Pudlak <[email protected]>
commit f3cc87dd1d7d59d843b5ad38a873bf6d32f60ca5
Author: Klaus Aehlig <[email protected]>
Date: Wed Jun 11 14:58:58 2014 +0200
Drop active flag in the worker pool
Given that now each process only runs a single job, there is no need
anymore to keep track about the worker pool being active. Hence drop
the corresponding code.
The only active use of the SetActive functionality is in the tests;
these tests, however, test priority handling in the worker pool,
which is not that important for single-worker worker pools anyway.
So we just remove the tests.
Signed-off-by: Klaus Aehlig <[email protected]>
Reviewed-by: Petr Pudlak <[email protected]>
commit 34a82110244ebbdfe97095e33de5205f85e1c774
Author: Klaus Aehlig <[email protected]>
Date: Wed Jun 11 14:33:22 2014 +0200
Remove drain flag in the jobs' job queue
As our jobs are running as processes, their job queue will
always only have a single entry. So there is no need to
prevent other jobs from entering when preparing a shut down.
Therefore, remove this code that is not needed any more.
Signed-off-by: Klaus Aehlig <[email protected]>
Reviewed-by: Petr Pudlak <[email protected]>
--
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
