How to auto-sync the new brick, after it has been added to a replica volume?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Everyone,

I have a replica volume, with two bricks:

Volume Name: c1
Type: Replicate
Status: Start
Number of Bircks: 1X2 = 2
Transport-type: tcp
Bricks:
Brick1: 192.168.0.1:/data
Brick2: 192.168.0.2:/data

I don't set any options an this volume. There has one mount point an 192.168.0.4:/mnt/c1

on 192.168.0.4:
ls /mnt/c1
file1 file2 file3

Now, I want add a brick(192.168.0.3:/data) to the volume c1, let the replica count from 2 to 3:

gluster volume add-brick c1 replica 3 192.168.0.3:/data

then, see the volume info, it works:

Volume Name: c1
Type: Replicate
Status: Start
Number of Bircks: 1X3 = 3
Transport-type: tcp
Bricks:
Brick1: 192.168.0.1:/data
Brick2: 192.168.0.2:/data
Brick3: 192.168.0.3:/data

Well, all about these is OK, but when I see the 192.168.0.3's /data, there has nothing for a long time.......

When I see the mount point an 192.168.0.4's /mnt/c1, the files begin transport to the 192.168.0.3's /data.

Although use this way can sync to the new brick, but it is not smart. How can it auto-sync to the new brick?


Thanks in advance for any info or tips!



_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux