Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-17 Thread Vijay Bellur
On Saturday 17 October 2015 08:14 PM, Lindsay Mathieson wrote: On 18 October 2015 at 00:17, Vijay Bellur mailto:vbel...@redhat.com>> wrote: Krutika has been working on several performance improvements for sharding and the results have been encouraging for virtual machine workloads.

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-17 Thread Udo Giacomozzi
Am 16.10.2015 um 18:51 schrieb Vijay Bellur: self-healing in gluster by default syncs only modified parts of the files from a source node. Gluster does a rolling checksum of a file needing self-heal to identify regions of the file which need to be synced over the network. This rolling checksu

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-17 Thread Lindsay Mathieson
On 18 October 2015 at 00:17, Vijay Bellur wrote: > Krutika has been working on several performance improvements for sharding > and the results have been encouraging for virtual machine workloads. > > Testing feedback would be very welcome! > Got to upgrade my cluster to jessie first :( Non trivi

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-17 Thread Vijay Bellur
On Saturday 17 October 2015 04:15 AM, Lindsay Mathieson wrote: On 17 October 2015 at 02:51, Vijay Bellur mailto:vbel...@redhat.com>> wrote: You may also want to check sharding (currently in beta with 3.7) where large files are chunked to smaller fragments. With this scheme, self-hea

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-17 Thread Vijay Bellur
On Saturday 17 October 2015 03:47 AM, Lindsay Mathieson wrote: On 17 October 2015 at 02:51, Vijay Bellur mailto:vbel...@redhat.com>> wrote: You may also want to check sharding (currently in beta with 3.7) where large files are chunked to smaller fragments. With this scheme, self-hea

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-16 Thread Lindsay Mathieson
On 17 October 2015 at 02:51, Vijay Bellur wrote: > You may also want to check sharding (currently in beta with 3.7) where > large files are chunked to smaller fragments. With this scheme, > self-healing (and rolling checksum computation thereby) happens only on > those fragments that undergo chan

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-16 Thread Lindsay Mathieson
On 17 October 2015 at 02:51, Vijay Bellur wrote: > You may also want to check sharding (currently in beta with 3.7) where > large files are chunked to smaller fragments. With this scheme, > self-healing (and rolling checksum computation thereby) happens only on > those fragments that undergo chan

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-16 Thread Vijay Bellur
On Friday 16 October 2015 08:11 PM, Lindsay Mathieson wrote: On 17 October 2015 at 00:26, Udo Giacomozzi mailto:udo.giacomo...@indunet.it>> wrote: To me this sounds like Gluster is not really suited for big files, like as the main storage for VMs - since they are being modified cons

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-16 Thread Lindsay Mathieson
On 17 October 2015 at 00:26, Udo Giacomozzi wrote: > To me this sounds like Gluster is not really suited for big files, like as > the main storage for VMs - since they are being modified constantly. > Depends :) Any replicated storage will have to heal its copies if they are written to when a n

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-16 Thread Lindsay Mathieson
On 16 October 2015 at 19:43, Udo Giacomozzi wrote: > So, in such a situation it would be normal that all Gluster files will be > healed afterwards? Given the time it takes and the network load measured it > apparently does *not *do a simple metadata check, but rather seems to > transfer the *cont

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-16 Thread Udo Giacomozzi
Am 16.10.2015 um 15:52 schrieb Ivan Rossi: looks like correct. during the reboot, if the vm write anything, at the end the files on #1 and #2 will be different from thos on #3 that was down. So healing is NECESSARY. Ivan Ok, I see. :-/ To me this sounds like Gluster is not really suited for

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-16 Thread Udo Giacomozzi
Am 16.10.2015 um 02:25 schrieb Lindsay Mathieson: On 15 October 2015 at 17:26, Udo Giacomozzi > wrote: My problem is, that every time I reboot one of the nodes, Gluster starts healing all of the files. Since they are quite big, it takes up to ~15-3

Re: [Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-15 Thread Lindsay Mathieson
On 15 October 2015 at 17:26, Udo Giacomozzi wrote: > My problem is, that every time I reboot one of the nodes, Gluster starts > healing all of the files. Since they are quite big, it takes up to ~15-30 > minutes to complete. It completes successfully, but I have to be extremely > careful not to m

[Gluster-users] Unnecessary healing in 3-node replication setup on reboot

2015-10-15 Thread Udo Giacomozzi
Hello everybody, I'm new to this list, apologies if I'm asking something stupid.. ;-) I'm using GlusterFS on three nodes as the foundation for a 3-node high-availability Proxmox cluster. GlusterFS is mostly used to store the HDD images of a number of VMs and is accessed via NFS. My problem i