Hi Jonathan,<br>comments are inlined.<br><br><div class="gmail_quote">On Tue, Nov 18, 2008 at 7:17 PM, Jonathan Endersby <span dir="ltr"><<a href="mailto:arbitraryuser@gmail.com">arbitraryuser@gmail.com</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;">Hi All<br><br>I've been looking for something like Gluster for a while and stumbled on it today via the wikipedia pages on Filesystems etc.<br>
<br>I have a few very very simple questions that might even be too simple to be on the FAQ, but if you think any of them are decent please add them there.<br>
<br>I think it might help if I start with what I want to achieve, then ask the questions. We want to build a high uptime, storage solution that can scale easily, but we want to do it on the cheap, with normal SATA disks and "consumer" motherboards etc. We'll use GigE to connect the nodes. Performance is not such a big criteria since the required throughput is nothing spectacular. <br>
<br>Based on what I've read I think we should use:<br><br>1. Unify translator (to present one big FS to my systems master server)<br>2. AFR (to make my data redundant ... I'd like to try and avoid using RAID on the nodes.)</blockquote>
<div><br>yes.<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>So my questions are:<br><br>1. Is there anything blindingly wrong with what I'm suggesting?</blockquote><div><br>no <br><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>2. Should I use AFR to achieve redundancy?</blockquote><div><br>yes.<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>2. What is the minimum number of machines/bricks in the cluster that will support data redundancy with AFR?</blockquote>
<div><br>two <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>
3. The AFR docs seem to indicate that it keeps a copy of the file on *every* node... isn't that wasting a lot of space? I really just need 2 copies or three copies so that one node or 2 nodes can go down at a time.</blockquote>
<div><br>afr has to be configured with as many children as the number of copies of the file has to be present. Hence as per your requirements, you can have only 2 or 3 nodes as children of afr and have the rest as children of unify.<br>
<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>I'm sure I'll have lots more questions but for now that should point me in the right direction.<br><br>Regards<br><font color="#888888">J.<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">regards,<br>-- <br>Raghavendra G<br><br>