FW: How does gluster identify which brick is the closest

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

 




-----Original Message-----
From: gluster-users-bounces@xxxxxxxxxxx [mailto:gluster-users-bounces@xxxxxxxxxxx] On Behalf Of Thai. Ngo Bao
Sent: Thursday, October 28, 2010 3:18 PM
To: gluster-users@xxxxxxxxxxx
Subject: [Gluster-users] How does gluster identify which brick is the closest

Hello all,

First of all, I would like to thank you for the great FS. I have some basic questions regarding Elastic Hash Algorithm (EHA).

I understand that EHA decides data placement at a host level and then places complete files on its selected storage. EHA also takes one step further and optimizes selection based not just on availability, but performance as well. Thus, if there is a copy of the file that is closer to the user, the closest copy is used.

So my questions are: How does gluster identify where the closest copy is? How does gluster identify which brick storing the copy closest to user? Which bricks are in a same or different subnets? Which value(s) does gluster take to compare for that purpose? Are they dynamic values, the results of EHA? Also, please point me out where are the code segments/modules of gluster doing these jobs.

I appreciate your time, and thank you in advance.

Regards,
Thai Ngo
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users



[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