[Gluster3.2@Grid5000] 128 nodes failure and rr scheduler question

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

 



Hello,

I'm driving some experiments on grid'5000 with GlusterFS 3.2 and, as a 
first point, i've been unable to start a volume featuring 128bricks (64 ok)

Then, due to the round-robin scheduler, as the number of nodes increase 
(every node is also a brick), the performance of an application on an 
individual node decrease!
So my question is : how to STOP the round-robin distribution of files 
over the bricks within a volume ?

*** Setup ***
- i'm using glusterfs3.2 from source
- every node is both a client node and a brick (storage)
Commands :
- gluster peer probe <each of the 128nodes>
- gluster volume create myVolume transport tcp <128 bricks:/storage>
- gluster volume start myVolume (fails with 128 bricks!)
- mount -t glusterfs ...... on all nodes

Feel free to tell me how to improve things

Fran?ois

-- 
-------------------------------------------------------------
THIEBOLT Francois \ Your computer seems overloaded ?
UPS Toulouse III  \ - Check that nobody's asked for tea !
thiebolt at irit.fr  \ "The Hitchhiker's Guide to the Galaxy" D.Adams



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux