On 02/13/2012 10:18 PM, Harry Mangalam wrote:
Is this documented anywhere? I'm in a position where this would be very
useful. I've posted a few queries about this as well and if the function
exists, it's an anonymous one.
Last year, Amar responded that:
"If you are in testing/validating phase, 3.3.0qa15 should have this
feature for you."
But there's no docs to point to how to do it. If the development docs
could be made available as a wiki or something similar, we stunt-testers
could provide feedback, examples of gotchas and edge cases, and what
works as expected that might have value.
One can do migrating of data within the existing bricks while
remove-brick by below command:
'gluster volume remove-brick <VOLNAME> <BRICK> start'
You can give more than 1 brick if needed. Also to check what is
happening, you can do below
'gluster volume remove-brick <VOLNAME> <BRICK> status'
Please wait for 3.3.0beta3, or else, even try later qa releases,
3.3.0beta2 doesn't have this feature.
Regards,
Amar
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
