[Gluster-devel] Don't allow data loss via add-brick (was Re: [Gluster-users] Add single server)

Pranith Kumar Karampuri pkarampu at redhat.com
Tue May 2 03:46:41 UTC 2017

Yeah it is a good idea. I asked him to raise a bug and we can move forward
with it.

On Mon, May 1, 2017 at 9:07 PM, Joe Julian <joe at julianfamily.org> wrote:

> On 04/30/2017 01:13 AM, lemonnierk at ulrar.net wrote:
>> So I was a little but luck. If I has all the hardware part, probably i
>>> would be firesd after causing data loss by using a software marked as
>>> stable
>> Yes, we lost our data last year to this bug, and it wasn't a test cluster.
>> We still hear from it from our clients to this day.
>> Is known that this feature is causing data loss and there is no evidence
>>> or
>>> no warning in official docs.
>>> I was (I believe) the first one to run into the bug, it happens and I
>> knew it
>> was a risk when installing gluster.
>> But since then I didn't see any warnings anywhere except here, I agree
>> with you that it should be mentionned in big bold letters on the site.
>> Might even be worth adding a warning directly on the cli when trying to
>> add bricks if sharding is enabled, to make sure no-one will destroy a
>> whole cluster for a known bug.
> I absolutely agree - or, just disable the ability to add-brick with
> sharding enabled. Losing data should never be allowed.
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170502/08c7bca7/attachment.html>

More information about the Gluster-devel mailing list