Distribute translator and differing brick sizes

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

 



Hi,

On Tue, Jan 27, 2009 at 3:27 AM, Sean Davis <sdavis2 at mail.nih.gov> wrote:

> If I am putting together several volumes of varying sizes using distribute,
> what type of load balancing should I expect?  I understand hashing and it
> sounds like if the disk fills, then it is not used, but can I use ALU
> scheduler to cut things off before the disk becomes full to allow for growth
> of directories and files?  How are people approaching this?


Distribute,  does not have any schedulers. The hashing as of now is sort of
static in the sense that if the disk becomes full, further creation of files
which happen to be scheduled to that node fail. Future versions of
distribute will reschedule the files to different nodes.


>
>
> Thanks,
> Sean
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
>
>


-- 
Raghavendra G
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://zresearch.com/pipermail/gluster-users/attachments/20090127/6f41de9c/attachment-0001.htm 


[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