Re: Deploying geo-replication to local peer

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

 



Hi Viktor,

Answers inline

On Wed, Jan 17, 2018 at 3:46 AM, Viktor Nosov <vnosov@xxxxxxxxxxxx> wrote:
Hi,

I'm looking for glusterfs feature that can be used to transform data between
volumes of different types provisioned on the same nodes.
It could be, for example, transformation from disperse to distributed
volume.
The possible option is to invoke geo-replication between volumes. It seems
is works properly.
But I'm concern about  requirement from Administration Guide for Red Hat
Gluster Storage 3.3 (10.3.3. Prerequisites):

"Slave node must not be a peer of the any of the nodes of the Master trusted
storage pool."

     This doesn't limit geo-rep feature in anyway. It's a  recommendation. You
can go ahead and use it.

Is this restriction is set to limit usage of geo-replication to disaster
recovery scenarios only or there is a problem with data synchronization
between
master and slave volumes?

Anybody has experience with this issue?

Thanks for any information!

Viktor Nosov


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



--
Thanks and Regards,
Kotresh H R
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.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