Hi Kotresh, Thanks for response! After taking more tests with this specific geo-replication configuration I realized that file extended attributes trusted.gfid and trusted.gfid2path.*** are synced as well during geo replication. I’m concern about attribute trusted.gfid because value of the attribute has to be unique for glusterfs cluster. But this is not a case in my tests. File on master and slave volumes has the same trusted.gfid attribute. To handle this issue the geo replication configuration option sync-xattrs = false was tested on glusterfs version 3.12.3. After changes of the option from true to false the geo-replication was stopped, volume was stopped, glusterd was stopped, glusterd was started, volume was started and the geo-replication was started again. It had no effect on syncing of trusted.gfid. How it is critical to have duplicated gfid’s? Can volume data be corrupted in this case somehow? Best regards, Viktor Nosov From: Kotresh Hiremath Ravishankar [mailto:khiremat@xxxxxxxxxx] Hi Viktor, Answers inline On Wed, Jan 17, 2018 at 3:46 AM, Viktor Nosov <vnosov@xxxxxxxxxxxx> wrote: Hi, This doesn't limit geo-rep feature in anyway. It's a recommendation. You can go ahead and use it.
Thanks and Regards, Kotresh H R |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
