On 08/08/2017 04:51 PM, Gerry O'Brien wrote:
Healing of contents works at the entire file level at the moment. For VM
image use cases, it is advised to enable sharding by virtue of which
heals would be restricted to only the shards that were modified when the
brick was down.
How are bricks healed in Debian Jessie 3.11? Is it at the file of
block level? The scenario we have in mind is a 2 brick replica volume
for storing VM file systems in a self-service IaaS, e.g. OpenNebula. If
one of the bricks is off-line for a period of time all the VM files
systems will all have been modified when brick comes back on-line. As
some of these VM file systems are quite large, 100GB+, our guess is that
if healing involves copying entire files then it might be unworkable for
us as the time to restore a few minutes downtime of a single brick could
take days. Just copying modified blocks would be fine.
Can someone give us some insight on how healing works?
Gluster-users mailing list