Karthick:
You should post this in maxscale group as well.
Dipti
On Fri, Oct 14, 2016 at 6:34 PM, Kristian Nielsen
wrote:
> Karthick Subramanian writes:
>
> > Below when I try at Slave DB:
> >
> > MariaDB [dr_repl]> select * from test_dr_repl;
> > Empty set (0.00 sec)
> >
> > MariaDB [dr_repl]
Karthick Subramanian writes:
> Below when I try at Slave DB:
>
> MariaDB [dr_repl]> select * from test_dr_repl;
> Empty set (0.00 sec)
>
> MariaDB [dr_repl]> commit;
> Query OK, 0 rows affected (0.00 sec)
>
> MariaDB [dr_repl]> select * from test_dr_repl;
> ++--+
> | id | val |
> ++-
I didn't expect that autocommit = OFF will affect the replication feature.
I thought replication will be handled irrespective what commit type is
enabled in the DB Server.
So whenever I promote any new master from a slave, I have to taken care
this auto commit accordingly. Is my understanding corr
Hi All,
I have the below topology:
Master -> Slave (using GTID replication)
Master -> Maxscale (Binlog Router)
Maxscale -> DR Site (via binlog router)
my.cnf is same across all sites:
lower-case-table-names=1
autocommit=0
#replication variables
log-bin=binlog
binlog-format=ROW
replicate_ann
4 matches
Mail list logo