Hi,<br><br><div class="gmail_quote">On Tue, Jan 27, 2009 at 3:27 AM, Sean Davis <span dir="ltr"><<a href="mailto:sdavis2@mail.nih.gov">sdavis2@mail.nih.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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?</blockquote>
<div><br>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.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>Thanks,<br><font color="#888888">Sean<br><br>
</font><br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Raghavendra G<br><br>