Gluster users - Nov 2016 - 3.7.16 with sharding corrupts VMDK files when adding and removing bricks

Il 12 nov 2016 12:53, "Kevin Lemonnier" <lemonnierk at
ulrar.net> ha scritto:
> Sure, but thinking about it later we realised that it might be for the
better.
> I believe when sharding is enabled the shards will be dispersed across
all the
> replica sets, making it that losing a replica set will kill all your VMs.
>
> Imagine a 16x3 volume for example, losing 2 bricks could bring the whole
thing
> down if they happen to be in the same replica set. (I might be wrong
about the
> way gluster disperse shards, it's my understanding only, never had the
chance
> to test it).
> With multiple small clusters, we have the same disk space in the end but
not
> that problem, it's a bit more annoying to manage but for now that's
allright.

I don't use EC because i really love the "gluster feature" to have
plain
files stored and not encoded in any way.
> Not really shocked there. Guess the cli should warn you when you try
re-setting
> the option though, that would be nice.
Exactly. I've proposed a warning in the cli when changing the shard size
but this is still unfixed and this is scaring me
it's a critical bug, IMHO, and should be addressed asap or any user could
destroy the whole cluster with a simple command and no warning at all.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20161112/2d2880f1/attachment.html>

On 12/11/2016 9:58 PM, Gandalf Corvotempesta wrote:
> Exactly. I've proposed a warning in the cli when changing the shard 
> size but this is still unfixed and this is scaring me
> it's a critical bug, IMHO, and should be addressed asap or any user 
> could destroy the whole cluster with a simple command and no warning 
> at all.
gluster volume reset <volname> *finger twitch*


And boom! volume gone.

Feature request: Ability to *lock* volume settings

-- 
Lindsay Mathieson