[Gluster-users] Urgent :) Procedure for replacing Gluster Node on 3.8.12

[Lindsay Mathieson]

On 9 June 2017 at 17:12, <lemonnierk at ulrar.net> wrote:

> Heh, on that, did you think to take a look at the Media_Wearout indicator ?
> I recently learned that existed, and it explained A LOT.
>

Yah, that has been useful in the past for journal/cache ssd's that get a
lot of writes. However all the stats on this boot SSD were ok, it just gave
up the ghost. Internal controller failure maybe.

I've started the process as above, seems to be going ok - cluster is going
to be unusable for the next couple of days.

Must admit this sort of process - replacing bricks and/or node is *very*
stressful with gluster. That sick feeling in the stomach - will I have to
restore everything from backups?

Shouldn't be this way.


-- 
Lindsay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170609/0137b78a/attachment.html>