Start by always testing on master.  Today's master is tomorrows release.  Todays release is yesterdays problem that won't be solved.
secondly, report issues to JIRA (after reproducing on master)


On Fri, Mar 13, 2015 at 9:48 AM, Joseph Dickson <jdickson@evolvetsi.com> wrote:
Yes, I can definitely see where master-master mode in MySQL can put
you in a pickle consistency wise..  I just wish Postgres was easier
with regard to fail-back.. failover isn't a problem, but getting
things to fail back requires rsync of data files, etc..

Before I set that up, I'd like to see sofia recover work in my
environment..  Currently it appears that the correct information is
being retrieved from the database, but that FS is hanging up the A leg
with INCOMPATIBLE_DESTINATION, and I can't quite understand the cause
behind that hangup.

Is there better logging that I can grab that might be more helpful?

Thanks!

On Thu, Mar 12, 2015 at 2:51 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
> I has used MySQL in master-master cluster and find it is unstable
> configuration. Many troubles with cluster consistence.
> I recommend use configuration master-slave with tools DB synchronization.
>
> Also migration to PostgreSQL cluster will be smart decision.
>




--
Anthony Minessale II       ♬ @anthmfs  ♬ @FreeSWITCH  ♬

☞ http://freeswitch.org/  ☞ http://cluecon.com/  ☞ http://twitter.com/FreeSWITCH
ClueCon Weekly Development Call 
☎ sip:888@conference.freeswitch.org  ☎ +19193869900