diff options
| author | Raghavendra Bhat <raghavendra@redhat.com> | 2012-08-23 15:32:33 +0530 |
|---|---|---|
| committer | Anand Avati <avati@redhat.com> | 2012-11-28 16:28:55 -0800 |
| commit | fbfcb0ad2aac73c2b5ab8950770c1184352bbf24 (patch) | |
| tree | d23af3c8a539da97e8f146ab19e4996cad6419c5 /cli/src/cli-xml-output.c | |
| parent | fadc34e7ce82f9e7f98f20e995cb2bbf71a00b20 (diff) | |
glusterd, cli: implement gluster system uuid reset command
A commonly faced problem among glusterfs users is: after a fresh
installation of glusterfs in a virtual machine, the VM image is
cloned to make multiple instances of the server. This breaks
glusterd because right after glusterfs installation on the first
boot glusterd would have created the node UUID and this gets
inherited into the clone. The result is wierd behavior at the time
of peer probe where glusterd does not (yet) deal with UUID
collisions in a user friendly way.
To handle it gluster peer reset command is implemented which upon
execution changes the uuid of local glusterd.
Change-Id: If207dd2ad93ab94ef1a3253f409c21c442975f87
BUG: 811493
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
Reviewed-on: http://review.gluster.org/3637
Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Anand Avati <avati@redhat.com>
Diffstat (limited to 'cli/src/cli-xml-output.c')
0 files changed, 0 insertions, 0 deletions