About spread count, lookup and layout

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

 



Hi
I have some question about spread count:

1. When I set spread count less than subvolume count, I see the hash is assigned to one directory layout for some subvolumes are zero (that is ok) , but I expect these subvolumes should not bee looked up in case lookup_everywhere for creating a file. Unfortunately I see these lookups in server profile.
Am I correct?
is there any way for this case to reduce the amount of lookups that is send to the servers? (lookup optimize is off and I want this)

2. I see the option for changing the spread count and fixing the layout in dht xlaor (dht_setxattr), but when I tried to set this attribute and change the layout I dont see any change!! while there is no error and crash (I call setfattr in client side because I dont see dht xlator in server graph)  
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux