Hi folks,
While debugging the migration issue, I noticed that sometimes we did in
fact occasionally hit but 987555 ("Address already in use") when doing a
live-migration, so I decided to implement the advice in aforementioned bug.
So I set 'option base-port 50152' in /etc/glusterfs/glusterd.vol (note
that the bug talks about /etc/glusterfs/gluster.vol, which doesn't
exist). The result of this was that migrations completely stopped
working. Trying to do a migration would cause the process on the sending
machine to hang, and on the receiving machine, libvirt became completely
unresponsive, even 'virsh list' would simply hang.
Curiously, 'gluster volume status' showed that, despite setting the
base-port to 50152, the bricks were still listening on 49152, as before
the config change & reboot.
I reverted my change to 'option-base-port', did another set of reboots,
and now migration is 'working' again, as in the guest gets moved across,
but then still loses access to its image (see my other mails).
Ubuntu 13.04, glusterfs-3.4.1.
Regards, Paul Boven.
--
Paul Boven <boven@xxxxxxx> +31 (0)521-596547
Unix/Linux/Networking specialist
Joint Institute for VLBI in Europe - www.jive.nl
VLBI - It's a fringe science
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
