> > Shortly after the sharded volume is made, there are some fuse mount > > messages. I'm not 100% sure if this was just before or during the > > big qemu-img command to make the 5T image > > (qemu-img create -f raw -o preallocation=falloc > > /adminvm/images/adminvm.img 5T) > Any reason to have a single disk with this size ? > Usually in any > virtualization I have used , it is always recommended to keep it lower. > Have you thought about multiple disks with smaller size ? Yes, because the actual virtual machine is an admin node/head node cluster manager for a supercomputer that hosts big OS images and drives multi-thousand-node-clusters (boot, monitoring, image creation, distribution, sometimes NFS roots, etc) . So this VM is a biggie. We could make multiple smaller images but it would be very painful since it differs from the normal non-VM setup. So unlike many solutions where you have lots of small VMs with their images small images, this solution is one giant VM with one giant image. We're essentially using gluster in this use case (as opposed to others I have posted about in the past) for head node failover (combined with pacemaker). > Also worth > noting is that RHII is supported only when the shard size is 512MB, so > it's worth trying bigger shard size . I have put larger shard size and newer gluster version on the list to try. Thank you! Hoping to get it failing again to try these things! ________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
