Comment #4 on issue 381 by [email protected]: Drain that doesn't force
master_candidate=no
http://code.google.com/p/ganeti/issues/detail?id=381
Sorry if I wasn't clear. What I was proposing was not to change the number
of candidates in gnt-node modify, but to allow Ganeti to go
temporarily "under" (which data-security wise has the same effect as
saying "reduce by one, then drain"). We could also have a safety that
doesn't allow going below some other value, perhaps, but the cluster value
would not be changed.
Thanks,
Guido
--
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
