Amar Tumballi wrote on Thu Oct 11 18:35:32 UTC 2012 :
> When we initially came up with specs of 'glusterd', we needed an
> option to replace a dead brick, and few people even requested for
> having an option to migrate the data from the brick, when we are
> replacing it.
Do you specifically mean
hi Amar,
I met across a problem when I replace a brick in a stripe-replicate volume.
I used both methods you mentioned in your post.
#gluster volume replace-brick brick1 brick2 start [1]
# gluster volume replace-brick brick1 brick2 commit force
(self-heal daemon heals the data)
the message shows
You may have noticed that I just wrote a blog article completely to the
contrary. I recently tried replacing a server using self-heal. It
brought the entire pool to a dead crawl and I had to pull the server
offline until after hours. My VM's all ended up read-only from lack of
response.
The r
Hi All,
When we initially came up with specs of 'glusterd', we needed an option
to replace a dead brick, and few people even requested for having an
option to migrate the data from the brick, when we are replacing it.
The result of this is 'gluster volume replace-brick' CLI, and in the
relea
