> Message: 1 > Date: Mon, 11 Aug 2014 09:53:30 -0400 (EDT) > From: Justin Clift <justin@xxxxxxxxxxx> > To: Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx> > Cc: gluster-users@xxxxxxxxxxx, Ray Mannings <manningsray1@xxxxxxxxx> > Subject: Re: Reading not distributed across bricks > Message-ID: > <417182971.4749068.1407765210056.JavaMail.zimbra@xxxxxxxxxx> > Content-Type: text/plain; charset=utf-8 > > ----- Original Message ----- > > hi Ray, > > Reads are served from the bricks which respond the fastest at the > > moment. They are not load-balanced. > > Maybe a good feature for 3.7? :) > Ray, There already is a feature, from gluster volume set help: "Option: cluster.read-hash-mode Description: inode-read fops happen only on one of the bricks in replicate. AFR will prefer the one computed using the method specified using this option 0 = first responder, 1 = hash by GFID of file (all clients use same subvolume), 2 = hash by GFID of file and client PID" This is particularly useful for benchmark tests, where the system may not have response time data sufficient to properly load balance and I have seen all the clients select the same replica using default value of 0. The value 2 is nice because if many clients are reading the same file, the load is distributed across bricks. -ben _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
