<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 1 February 2017 at 19:30, Jesper Led Lauridsen TS Infra server <span dir="ltr"><<a href="mailto:JLY@dr.dk" target="_blank">JLY@dr.dk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Arbiter, isn't that only used where you want replica, but same storage space.<br>
<br>
I would like a distributed volume where I can write, even if one of the bricks fail. No replication.<br>
<br></blockquote><div><br></div><div>DHT does not currently allow that as that could lead to differnt files with duplicate names on different bricks.</div><div><br></div><div>Regards,</div><div>Nithya</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks<br>
Jesper<br>
<br>
> -----Oprindelig meddelelse-----<br>
> Fra: Cedric Lemarchand [mailto:<a href="mailto:yipikai7@gmail.com">yipikai7@gmail.com</a>]<br>
> Sendt: 1. februar 2017 13:41<br>
> Til: Jesper Led Lauridsen TS Infra server <<a href="mailto:JLY@dr.dk">JLY@dr.dk</a>><br>
> Cc: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> Emne: Re: [Gluster-users] Always writeable distributed volume<br>
<div class="HOEnZb"><div class="h5">><br>
> Short answer : I think you need to add an arbiter node, this way the cluster<br>
> keeps being writable when there is at least 2 nodes presents (eg 1 data node<br>
> is down). This solve the split brain case where only 2 nodes are involved in<br>
> the setup.<br>
><br>
> Cheers<br>
><br>
> --<br>
> Cédric Lemarchand<br>
><br>
> > Le 1 févr. 2017 à 13:18, Jesper Led Lauridsen TS Infra server <<a href="mailto:JLY@dr.dk">JLY@dr.dk</a>> a<br>
> écrit :<br>
> ><br>
> > Hi,<br>
> ><br>
> > I am wondering if it is possible to create an always writeable distributed<br>
> volume.<br>
> ><br>
> > Reading the documentation I can figure out how. So is it possible?<br>
> > If I understand the docs correctly. The DHT determines based on a hash of<br>
> the filename, which brick to place the file. And if you have two bricks and<br>
> loose one brick I can't create files DHT determines should be places on the<br>
> failed brick.<br>
> ><br>
> > I have tried creating a distributed volume on two bricks/nodes. And as the<br>
> feared I can't write files DHT determines should be placed on a failed node. I<br>
> am well aware and can accept that I can't access or re-create files already<br>
> created on the failed node. But I would like to write new files.<br>
> ><br>
> > Is there a setting/feature I can enable that allows me to create file on the<br>
> available/online bricks even if DHT determines that the file should be placed<br>
> on the unavailable/failed?<br>
> ><br>
> > My use case is: I want to use a Gluster volume for temporary storage that is<br>
> always available, as in I can always mount and write to it . We have a lot of<br>
> media file that is transcoded on user request and there need at temporary<br>
> storage for this operation. All I need is a temporary, fast and always<br>
> accessible storage with no data security/replica.<br>
> ><br>
> > Regards<br>
> > Jesper<br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Gluster-users mailing list<br>
> > <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> > <a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a></div></div></blockquote></div><br></div></div>