<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
is this ( <a href="http://gluster.org/pipermail/gluster-users/2011-July/008223.html" target="_blank">http://gluster.org/pipermail/<u></u>gluster-users/2011-July/<u></u>008223.html</a> ) true regarding 3.3.0 beta or should check out GIT?<br>
</blockquote><div><br></div><div>This feature is not in 3.3.0beta. You have to checkout the GIT head (master branch). </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Also while it is possible to manually create in client volfile will some more complex setups like striped+replicated+distributed setups ( like for example stripe on 6 (or more) nodes each stripe having 3 replicas and distributed on 12 servers) be supported or better stay away from something like that?<br>
<br></blockquote><div> </div><div>Try not to come up with manual configuration, as it would be hard to support that in long run. In 3.3.0 release, it should be possible to have distribute-stripe-replica too. But for your setup, it will be requiring lot of bricks (as per your description, you would need 12 x 6 x 3 = 216 bricks).</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
What's the suggested way to store large ~500 Gb files in reliable way so it doesn't bring the cluster down if a replica fails and has to be resynced.<br>
<br></blockquote><div>Stripe + replica would do the job.</div><div> </div><div>Regards,</div><div>Amar</div></div><br>