For the last question, we instruct the administrator of each client to use "fs setserverprefs" to set preference. The server proximity is known a priori. Our IT tries to arrange the IP addresses such that clients stay within the same subnet to their closest servers, and different sites use different subnets. In the cases where IP similarity does not fully represent network distance, "fs setserverprefs" is used to manually override the preference.
-----Original Message----- From: Jeffrey Altman [mailto:jalt...@auristor.com] Sent: Monday, August 6, 2018 10:29 AM To: Ximeng Guan <x...@royole.com>; openafs-info@openafs.org Subject: Re: [OpenAFS] Does vos release/volume replication always initiates data transfer from RW site? In OpenAFS, all of the "smarts" are in the vos process. This process has no knowledge of the network topology which is why OpenAFS has difficulties in network environments that lack full end-to-end connectivity between all peers. In theory, someone could write a volserver topology map that could be provided to "vos" as input. It could be used in conjunction with the volume site list from the location service to decide how to replicate the volumes. The OpenAFS location service doesn't provide clients (cache managers) any locality information and the Unix cache manager does not rank volume sites based upon performance characteristics. How are you ensuring that clients contact the local fileserver? Jeffrey Altman :�� T���&j)b� b�өzpJ)ߢ�^��좸!��l��b��(���~�+��Y���b�ا~����~ȧ~
