Hi Dave,
I see, thank you. What I am planning to do:
1. Write on the master
2. Read from the slave (if the file is not on the slave, then search on
the master).
What do you think about?
-- Kindest regards,
Milos Cuculovic
IT Manager
--
MDPI AG
Postfach, CH-4005 Basel, Switzerland
Office: Klybeckstrasse 64, CH-4057 Basel, Switzerland
Tel. +41 61 683 77 35
Fax +41 61 302 89 18
Email: cuculovic@xxxxxxxx
Skype: milos.cuculovic.mdpi
On 16.07.2015 00:23, Dave Warren wrote:
On 2015-07-15 00:13, Milos Cuculovic - MDPI wrote:
Thank you for your reply.
You're right, the configuration you mentioned is the right one.
The problem with the solution 1 is that I need bi-directional sync.
The solution 2 is also not possible, I need to allow users to write on
both places in the same time.
I saw there is a possibility to do GlusterFS Distribute to Replica, I
tried this out but the synchronization is done synchronous, so it
takes time to do it and it is very slow.
Any solution?
I don't believe there is a way to do this within Gluster itself,
geo-replication is only a one-way solution by design.
If you can deal with asynchronous sync between the geo sites, you could
use something like unison to synchronize two independent gluster
volumes. This is obviously messy since it introduces separate software
into the mix which could require it's own maintenance.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
