[Gluster-users] Brick Preference

[Andy Pace]

Good call.


However, when running scale-n-defrag.sh (not supposed to run defrag.sh standalone apparently), i get a lot of errors:

find: `setfattr': No such file or directory
find: `setfattr': No such file or directory
find: `setfattr': No such file or directory
find: `setfattr': No such file or directory
find: `setfattr': No such file or directory
find: `setfattr': No such file or directory
find: `setfattr': No such file or directory

is it safe to ignore thouse? because it seems to have defragged anyway:

Defragmenting directory /distributed//29150 (/root/defrag-store-29150.log)
Completed directory /distributed//29150
Defragmenting directory /distributed//29216 (/root/defrag-store-29216.log)
Completed directory /distributed//29216
Defragmenting directory /distributed//images (/root/defrag-store-images.log)
Completed directory /distributed//images
Defragmenting directory /distributed//installers (/root/defrag-store-installers.log)
Completed directory /distributed//installers
Defragmenting directory /distributed//scripts (/root/defrag-store-scripts.log)
Completed directory /distributed//scripts

-----Original Message-----
From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Harshavardhana
Sent: Thursday, June 24, 2010 2:10 AM
To: gluster-users at gluster.org
Subject: Re: [Gluster-users] Brick Preference

On 06/23/2010 01:53 PM, Andy Pace wrote:
> Just wondering how Gluster determines which brick to send files to. I've got 4 bricks setup right now, and benchmarking 4 clients against them, and it seems that all the clients prefer bricks 3 and 4, rather than 1 and 2...
>
> It's setup in a replicating/distributing model.
>
> Is there a way to 'weight' them? It would make sense for doing this on commodity hardware, as Gluster advertises - send less traffic to smaller bricks, and more to the bigger bricks.
>
>
>
>    
Hi Andy,

       Are you using the brick4 and brick4 from the same set of subvolume from the last time?.
       Since updating the replicate/distribute pairs you might need to run defrag.sh scripts to
       repopulate the hash values properly.  Also this is the case when you don't defrag the older
       directories on old exports gets files written to their own set of pairs.  Only new
       directories would help in creating files across evenly.

Regards

--
Harshavardhana
Gluster Inc - http://www.gluster.com
+1(408)-770-1887, Ext-113
+1(408)-480-1730


_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users