Open GoogleCodeExporter opened 9 years ago
We do this because of an internal restriction - we track whether disks are
active or not via a single flag. The newly added disk must be active to
synchronize, while already existing disks have been deactivated during
shutdown, or not activated at all. Having the disks both active and inactive
violates assumptions and causes errors across the codebase, so we force
ourselves into consistency in the only way that still preserves redundancy -
waiting for the sync to complete before shutting down the disk.
This is something that could be improved in a newer Ganeti version where disks
are separate objects, but there is no possible way we can port this to 2.11.
I'm keeping this bug around, but setting the version to 2.14. Let me know if
anything else is needed - perhaps a manpage update?
Original comment by r...@google.com
on 17 Dec 2014 at 12:40
I note that --no-wait-for-sync can be used on with gnt-instance modify -t drbd;
maybe it's because *all* the disks are activated in that instance?
If it's OK to activate the disks on a shutdown instance, maybe a workaround is
to use "gnt-instance activate-disks" before adding the new disk?
Otherwise, yes I think a documentation update is in order. Currently it just
says:
"Per default, gnt-instance waits for the disk
mirror to sync.
If you do not want this behavior, use the ``--no-wait-for-sync`` option."
so add a note explaining under what circumstances this can be done. I guess
--hotplug on a running instance is one of them?
Original comment by bcandler...@googlemail.com
on 24 Dec 2014 at 9:40
Original issue reported on code.google.com by
bcandler...@googlemail.com
on 15 Dec 2014 at 10:33