<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 30, 2017 at 1:43 PM, <span dir="ltr"><<a href="mailto:lemonnierk@ulrar.net" target="_blank">lemonnierk@ulrar.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">> So I was a little but luck. If I has all the hardware part, probably i<br>
> would be firesd after causing data loss by using a software marked as stable<br>
<br>
</span>Yes, we lost our data last year to this bug, and it wasn't a test cluster.<br>
We still hear from it from our clients to this day.<br>
<span class="gmail-"><br>
> Is known that this feature is causing data loss and there is no evidence or<br>
> no warning in official docs.<br>
><br>
<br>
</span>I was (I believe) the first one to run into the bug, it happens and I knew it<br>
was a risk when installing gluster.<br>
But since then I didn't see any warnings anywhere except here, I agree<br>
with you that it should be mentionned in big bold letters on the site.<br></blockquote><div><br></div><div>After discussion with 3.10 release maintainer, this was added in release-notes of 3.10.1: <a href="https://github.com/gluster/glusterfs/blob/release-3.10/doc/release-notes/3.10.1.md">https://github.com/gluster/glusterfs/blob/release-3.10/doc/release-notes/3.10.1.md</a><br><br></div><div>But you are right in the sense that just this much documentation doesn't do enough justice.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Might even be worth adding a warning directly on the cli when trying to<br>
add bricks if sharding is enabled, to make sure no-one will destroy a<br>
whole cluster for a known bug.<br></blockquote><div><br></div><div>Want to raise a bug on 'distribute' component? If you don't have the time let me know I will do the needful.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
> Il 30 apr 2017 12:14 AM, <<a href="mailto:lemonnierk@ulrar.net">lemonnierk@ulrar.net</a>> ha scritto:<br>
><br>
> > I have to agree though, you keep acting like a customer.<br>
> > If you don't like what the developers focus on, you are free to<br>
> > try and offer a bounty to motivate someone to look at what you want,<br>
> > or even better : go and buy a license for one of gluster's commercial<br>
> > alternatives.<br>
> ><br>
> ><br>
> > On Sat, Apr 29, 2017 at 11:43:54PM +0200, Gandalf Corvotempesta wrote:<br>
> > > I'm pretty sure that I'll be able to sleep well even after your block.<br>
> > ><br>
> > > Il 29 apr 2017 11:28 PM, "Joe Julian" <<a href="mailto:joe@julianfamily.org">joe@julianfamily.org</a>> ha scritto:<br>
> > ><br>
> > > > No, you proposed a wish. A feature needs described behavior, certainly<br>
> > a<br>
> > > > lot more than "it should just know what I want it to do".<br>
> > > ><br>
> > > > I'm done. You can continue to feel entitled here on the mailing list.<br>
> > I'll<br>
> > > > just set my filters to bitbucket anything from you.<br>
> > > ><br>
> > > > On 04/29/2017 01:00 PM, Gandalf Corvotempesta wrote:<br>
> > > ><br>
> > > > I repeat: I've just proposed a feature<br>
> > > > I'm not a C developer and I don't know gluster internals, so I can't<br>
> > > > provide details<br>
> > > ><br>
> > > > I've just asked if simplifying the add brick process is something that<br>
> > > > developers are interested to add<br>
> > > ><br>
> > > > Il 29 apr 2017 9:34 PM, "Joe Julian" <<a href="mailto:joe@julianfamily.org">joe@julianfamily.org</a>> ha<br>
> > scritto:<br>
> > > ><br>
> > > >> What I said publicly in another email ... but not to call out my<br>
> > > >> perception of your behavior publicly if also like to say:<br>
> > > >><br>
> > > >> Acting adversarial doesn't make anybody want to help, especially not<br>
> > me<br>
> > > >> and I'm the user community's biggest proponent.<br>
> > > >><br>
> > > >> On April 29, 2017 11:08:45 AM PDT, Gandalf Corvotempesta <<br>
> > > >> <a href="mailto:gandalf.corvotempesta@gmail.com">gandalf.corvotempesta@gmail.<wbr>com</a>> wrote:<br>
> > > >>><br>
> > > >>> Mine was a suggestion<br>
> > > >>> Fell free to ignore was gluster users has to say and still keep going<br>
> > > >>> though your way<br>
> > > >>><br>
> > > >>> Usually, open source project tends to follow users suggestions<br>
> > > >>><br>
> > > >>> Il 29 apr 2017 5:32 PM, "Joe Julian" <<a href="mailto:joe@julianfamily.org">joe@julianfamily.org</a>> ha<br>
> > scritto:<br>
> > > >>><br>
> > > >>>> Since this is an open source community project, not a company<br>
> > product,<br>
> > > >>>> feature requests like these are welcome, but would be more welcome<br>
> > with<br>
> > > >>>> either code or at least a well described method. Broad asks like<br>
> > these are<br>
> > > >>>> of little value, imho.<br>
> > > >>>><br>
> > > >>>><br>
> > > >>>> On 04/29/2017 07:12 AM, Gandalf Corvotempesta wrote:<br>
> > > >>>><br>
> > > >>>>> Anyway, the proposed workaround:<br>
> > > >>>>> <a href="https://joejulian.name/blog/how-to-expand-glusterfs-replicat" rel="noreferrer" target="_blank">https://joejulian.name/blog/<wbr>how-to-expand-glusterfs-<wbr>replicat</a><br>
> > > >>>>> ed-clusters-by-one-server/<br>
> > > >>>>> won't work with just a single volume made up of 2 replicated<br>
> > bricks.<br>
> > > >>>>> If I have a replica 2 volume with server1:brick1 and<br>
> > server2:brick1,<br>
> > > >>>>> how can I add server3:brick1 ?<br>
> > > >>>>> I don't have any bricks to "replace"<br>
> > > >>>>><br>
> > > >>>>> This is something i would like to see implemented in gluster.<br>
> > > >>>>><br>
> > > >>>>> 2017-04-29 16:08 GMT+02:00 Gandalf Corvotempesta<br>
> > > >>>>> <<a href="mailto:gandalf.corvotempesta@gmail.com">gandalf.corvotempesta@gmail.<wbr>com</a>>:<br>
> > > >>>>><br>
> > > >>>>>> 2017-04-24 10:21 GMT+02:00 Pranith Kumar Karampuri <<br>
> > > >>>>>> <a href="mailto:pkarampu@redhat.com">pkarampu@redhat.com</a>>:<br>
> > > >>>>>><br>
> > > >>>>>>> Are you suggesting this process to be easier through commands,<br>
> > > >>>>>>> rather than<br>
> > > >>>>>>> for administrators to figure out how to place the data?<br>
> > > >>>>>>><br>
> > > >>>>>>> [1] <a href="http://lists.gluster.org/pipermail/gluster-users/2016-July/0" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>pipermail/gluster-users/2016-<wbr>July/0</a><br>
> > > >>>>>>> 27431.html<br>
> > > >>>>>>><br>
> > > >>>>>> Admin should always have the ability to choose where to place<br>
> > data,<br>
> > > >>>>>> but something<br>
> > > >>>>>> easier should be added, like in any other SDS.<br>
> > > >>>>>><br>
> > > >>>>>> Something like:<br>
> > > >>>>>><br>
> > > >>>>>> gluster volume add-brick gv0 new_brick<br>
> > > >>>>>><br>
> > > >>>>>> if gv0 is a replicated volume, the add-brick should automatically<br>
> > add<br>
> > > >>>>>> the new brick and rebalance data automatically, still keeping the<br>
> > > >>>>>> required redundancy level<br>
> > > >>>>>><br>
> > > >>>>>> In case admin would like to set a custom placement for data, it<br>
> > should<br>
> > > >>>>>> specify a "force" argument or something similiar.<br>
> > > >>>>>><br>
> > > >>>>>> tl;dr: as default, gluster should preserve data redundancy<br>
> > allowing<br>
> > > >>>>>> users to add single bricks without having to think how to place<br>
> > data.<br>
> > > >>>>>> This will make gluster way easier to manage and much less error<br>
> > prone,<br>
> > > >>>>>> thus increasing the resiliency of the whole gluster.<br>
> > > >>>>>> after all , if you have a replicated volume, is obvious that you<br>
> > want<br>
> > > >>>>>> your data to be replicated and gluster should manage this on it's<br>
> > own.<br>
> > > >>>>>><br>
> > > >>>>>> Is this something are you planning or considering for further<br>
> > > >>>>>> implementation?<br>
> > > >>>>>> I know that lack of metadata server (this is a HUGE advantage for<br>
> > > >>>>>> gluster) means less flexibility, but as there is a manual<br>
> > workaround<br>
> > > >>>>>> for adding<br>
> > > >>>>>> single bricks, gluster should be able to handle this<br>
> > automatically.<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>
> > > >>>>><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>
> > > >>>><br>
> > > >>><br>
> > > >> --<br>
> > > >> Sent from my Android device with K-9 Mail. Please excuse my brevity.<br>
> > > >><br>
> > > ><br>
> > > ><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>
> ><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>
> ><br>
</div></div><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></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>