On Tue, May 2, 2017 at 9:16 AM, Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx> wrote:
Yeah it is a good idea. I asked him to raise a bug and we can move forward with it.
+Raghavendra/Nitya who can help with the fix.
On Mon, May 1, 2017 at 9:07 PM, Joe Julian <joe@xxxxxxxxxxxxxxxx> wrote:
On 04/30/2017 01:13 AM, lemonnierk@xxxxxxxxx wrote:
So I was a little but luck. If I has all the hardware part, probably iYes, we lost our data last year to this bug, and it wasn't a test cluster.
would be firesd after causing data loss by using a software marked as stable
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 orI was (I believe) the first one to run into the bug, it happens and I knew it
no warning in official docs.
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@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
--Pranith
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
--
Pranith
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
