On 06/04/2012 07:15 PM, Amar Tumballi wrote:
Do you know if I'll be able to convert a distribute to
distribute-replicate this way?
1) delete the distribute volume
2) create a distribute-replicate volume
3) run the self-heal, which hopefully results in the data moved to the
other brick, *not* removed?
With 3.3.0 release, for all these three steps can be achieved by one
step, do just
bash# gluster volume add-brick <VOLNAME> replica N BRICK1 BRICK2 .. BRICKn
where,
VOLNAME is distribute volume name
N is target replica count (in this case 2, as with one add-brick command
you can increase replica count only by 1).
BRICK(1-n) is gluster brick to be added as pair to each existing bricks
in order.
Let the proactive self-heal daemon take care of syncing your data :-)
Hmm, but the steps you describe (gluster volume add-brick <VOLNAME>
replica N ...), assuming I upgrade to 3.3:
1) my volume is "distribute" right now - "will gluster volume add-brick
<VOLNAME> replica N ..." work in that case?
2) I don't have any bricks to add; all are existing already
3) with 1) and 2) above - does it mean I have to delete the distribute
volume, create it as distribute+replicate over the existing data, and
hope it will mirror the data, not remove it (I'm concern that xattrs
will be somehow confusing glusterfs)
--
Tomasz Chmielewski
http://www.ptraveler.com
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
