In the User Guide: http://www.gluster.com/community/documentation/index.php/User_Guide#Replicate "The next release of GlusterFS will add the following features: *Ability to specify the sub-volume from which read operations are to be done (this will help users who have one of the sub-volumes as a local storage volume). *Allow scheduling of read operations amongst the sub-volumes in a round-robin fashion." Is the "next release" that it refers to 3.0.0? Or is the "next release" the one after 3.0.0? The ability to specify the sub-volume from which to read would be really useful for the way I want to deploy glusterfs. Thanks for any clarification. -- Jiann-Ming Su "I have to decide between two equally frightening options. If I wanted to do that, I'd vote." --Duckman "The system's broke, Hank. The election baby has peed in the bath water. You got to throw 'em both out." --Dale Gribble "Those who vote decide nothing. Those who count the votes decide everything.? --Joseph Stalin
Jiann-Ming Su wrote:> In the User Guide: > http://www.gluster.com/community/documentation/index.php/User_Guide#Replicate > > "The next release of GlusterFS will add the following features: >Both are already in 3.0.0> *Ability to specify the sub-volume from which read operations are to > be done (this will help users who have one of the sub-volumes as a > local storage volume). >This can be done by setting the option "read-subvolume" for replicate. Its value should be the name of the subvolume you want to be used for reads.> *Allow scheduling of read operations amongst the sub-volumes in a > round-robin fashion." >In the absence of the read-subvolume option, each file gets its read-subvolume defined in a round-robin fashion, so that provides a measure of load balancing. Vikas -- Engineer - Gluster, Inc.