Comment #1 on issue 381 by [email protected]: Drain that doesn't force
master_candidate=no
http://code.google.com/p/ganeti/issues/detail?id=381
I don't think this is the right solution.
The reason why draining a node makes it a non-MC is that MCs are critical
to the functioning of Ganeti. If a MC is down, all jobs operations are
slowed down, restarting masterd (if needed) will be slower, etc.
If you're worried about promotions, why not simply set the pool size
temporarily to a smaller number, then drain/reboot/undrain as needed, and
only at the end of all operations increase the pool size again? That way,
you will only have to wait at the end for replication of jobs (eventually
after you have run a job archive).
--
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
