[Gluster-devel] bit rot
Raghavendra Bhat
rabhat at redhat.com
Wed Jan 7 07:18:11 UTC 2015
Hi,
As per the design dicussion it was mentioned that, there will be one
BitD running per node which will take care of all the bricks of all the
volumes running on that node. But, here once thing that becomes
important is doing graph changes for the BitD process upon
enabling/disabling of bit-rot functionality for the volumes. With more
and more graph changes, there is more chance of BitD running out of
memory (as of now the older graphs in glusterfs are not cleaned up).
So for now it will be better to have one BitD per volume per node. In
this case, there will not be graph changes in BitD. It will be started
for a volume upon enabling bit-rot functionality for that volume and
will be brought down when bit-rot is disabled for a volume.
Regards,
Raghavendra Bhat
More information about the Gluster-devel
mailing list