Failsafe replication between two DC - getting trash in files.

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

 



Hi Alex - ?????? ???? (?? ??????? ???? ?????)

The problem with replication on both the server and the client is that the server does not (I believe) have an awareness of what the client is doing. I did post a thread asking about best practices for replication (I was leaning towards server side to keep that traffic local), and was told that client side replication was recommended and supported.

I think you're seeing corruption on your copies because both the client and the server are replicating.

Also - the reason you didn't get an email directly from me last time was that I only send to the list unless requested otherwise. I'm copying you directly this time.

Thanks,

James Burnash, Unix Engineering


-----Original Message-----
From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Alexander Voronin
Sent: Tuesday, October 05, 2010 9:30 AM
To: gluster-users at gluster.org
Subject: Re: Failsafe replication between two DC - getting trash in files.

Mailing list seems to be very slow. I still did not get answer from James Burnash. So wh not have replication on client and server side? It's seems to be logical, I've just extended this sample http://www.gluster.com/community/documentation/index.php/Setting_up_AFR_on_two_servers_with_server_side_replication

--
????? ? ????????? ?? ????? ???, ????? ??? ?????????..


DISCLAIMER: 
This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. 
NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at its discretion, monitor and review the content of all e-mail communications. http://www.knight.com


[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