Hello I am using Glusterfs 3.10.5 on CentOS7. A replicated distributed volume with a dist-rep hot tier. During data migration, we noticed the tierd.log on one of nodes was huge. Upon review it seemed to be stuck on a certain set of files. Running a "gluster vol heal VOL info" showed that those same files caused problems in the tier, were in split brain. So we went to fix split brain, we used "source-brick" and chose
each of the bricks as the master to heal from.
However when we ran the heal command above, It spit out that each file was not in split brain and that it healed 0. We then double checked the status of the files listed in heal info output with :
And it reported that the files were not in split brain.... Any insight would be greatly appreciated. Brett |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users