rsync to gluster mount: self-heal and bad performance

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

 



Hello,

While rsyncing to a directory mounted through glusterfs fuse, performance is very bad and it appears every synced file generates a (metadata) self-heal. 

The volume is mounted with option acl and acl's are set on a subdirectory.

Setup is as follows:

Two Centos 7 VM's (KVM), with Gluster 3.7.6 and one physical CentOS 6 node, also Gluster 3.7.6. Physical node functions as arbiter. So it's a replica 3 arbiter 1 volume. The bricks are LVM's with XFS filesystem.

While I don't think I should expect top performance for rsync on Gluster, I wouldn't expect every file synced to trigger a self-heal. Anything I can do to improve this? Should I file a bug?

Another thing that looks related, I see a lot of these messages, especially when doing IO:

[2015-11-12 19:25:42.185904] I [dict.c:473:dict_get] (-->/usr/lib64/glusterfs/3.7.6/xlator/debug/io-stats.so(io_stats_lookup_cbk+0x121) [0x7fdcc2d31161] -->/usr/lib64/glusterfs/3.7.6/xlator/system/posix-acl.so(posix_acl_lookup_cbk+0x242) [0x7fdcc2b1b212] -->/lib64/libglusterfs.so.0(dict_get+0xac) [0x7fdcd5e770cc] ) 0-dict: !this || key=system.posix_acl_default [Invalid argument]


--
Tiemen Ruiten
Systems Engineer
R&D Media
_______________________________________________
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