Re: Change underlying brick on node

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Tue, Aug 9, 2016 at 2:18 AM, Lindsay Mathieson <lindsay.mathieson@xxxxxxxxx> wrote:
On 9 August 2016 at 12:23, David Gossage <dgossage@xxxxxxxxxxxxxxxxxx> wrote:
> Since my dev is now on 3.8 and has granular enabled I'm feeling too lazy to
> roll back so will just wait till 3.8.2 is released in few days that fixes
> the bugs mentioned to me and then test this few times on my dev.
>
> Would be nice if I could get to a point where I could have one brick dead
> and doing a full heal and not have every VM pause while shards heal, but I
> may be asking too much when dealing with a rather heavy recovery.


I tested Joe's method with my dev cluster, worked perfectly. The *one*
running VM on it didn't seem to badly affected, but it was already
very slow :)

3.7 or 3.8?  And if 3.8 did you have that new granular-entry-heal  feature enabled? 


Thanks Joe.

--
Lindsay

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux