Thanks for pointing to the article. I have been following the article all the way. What intrigues me is the dht values associated with sub directories. [root@glusterhackervm3 glus]# getfattr -n trusted.glusterfs.dht -e hex /brick2/vol getfattr: Removing leading '/' from absolute path names # file: brick2/vol trusted.glusterfs.dht=0x00000001000000007ffffde2ffffffff
[root@glusterhackervm3 glus]# getfattr -n trusted.glusterfs.dht -e hex /brick2/vol/d/ getfattr: Removing leading '/' from absolute path names # file: brick2/vol/d/ trusted.glusterfs.dht=0x0000000100000000000000007ffffffe Does it mean that only files whose DHT value ranges from
0x00 to 0x7ffffffe
can be saved inside the ‘d’ directory. But then it provides a very narrow range of
0x7ffffde2 to 0x7ffffffe to be created in that directory.
Thanks and Regards, Ram From: gluster-users-bounces@xxxxxxxxxxx [mailto:gluster-users-bounces@xxxxxxxxxxx]
On Behalf Of Joe Julian Here's an article explaining how dht works. The hash maps are per-directory. https://joejulian.name/blog/dht-misses-are-expensive/ On 11/08/2016 11:04 AM, Ankireddypalle Reddy wrote:
***************************Legal Disclaimer*************************** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." **********************************************************************
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users