php - MySQL replication issues with recording client history -
i have 2 lamp servers, master , slave.
the master's web root gets mirrored onto slave using rsync, , databases replicated onto slave using mysql replication.
the master in on our office lan. use capture data , generate reports. slave clients access use our website.
all client activity needs saved database. obvious problem if slave allowed write database, goes out of sync master.
if slave becomes unavailable, client traffic redirected temporarily use master (dns failover)
do have ideas recording client activity database without breaking master/slave sync.
so far best can come not replicate database containing client usage history. risky not replicate tables
how .... switching roles, old master slave , old slave becomes master. therefore, shouldnt run sync-problems mentioned.
as "ps", use alternate database that. tables need sync-ed in 1 database, non-synced in other db.
Comments
Post a Comment