Re: self healing with sharding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2016-07-08 11:23 GMT+02:00 Kevin Lemonnier <lemonnierk@xxxxxxxxx>:
> No, only the shards that were modified during the downtime of the node
> will need to be healed. It is MUCH quicker than healing the whole
> VM file without sharding, and shouldn't provoke a freez of the VM
> because of locking.

This is not clear to me, due to my low understanding of gluster.

Let's assume a 100GB virtual machine image (qcow2 or whatelse) with 64MB shards
One users does this: "touch /tmp/test" inside this virtual machine,
during the node downtime.
Gluster will "update" only the involved shard, right ?
Thus, when node comes back, only that single shard must be healed,
maybe a 64MB shard on a 100GB image.

Without sharding, a single "touch" would require the whole 100GB to be sharded ?

What happens to the virtual machine, during the shard healing? Only
files included in that shard are set as read-only? Or all files
included in that shard are hidden ?
What if a file is spread across multiple shards and one of these
shards need healing ?
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux