It's good to know. Keep up with good work, cheers!!
--
*Wagner Bianchi, MySQL Database Specialist*
Mobile: +55.31.8654.9510
E-mail: m...@wagnerbianchi.com
Twitter: @wagnerbianchijr
2014-09-06 3:01 GMT-03:00 Ajay Garg ajaygargn...@gmail.com:
Hi Wagner.
That is what I did as the last
Hi Wagner.
That is what I did as the last resort, and that is only what solved the issue.
Thanks.
On Fri, Sep 5, 2014 at 1:52 AM, wagnerbianchi.com m...@wagnerbianchi.com
wrote:
You can try these steps:
1-) Stop slave and write down the replication coordinates getting that in
MySQL's
Hi all.
Unfortunately, I have run into the logs, as described at
http://bugs.mysql.com/bug.php?id=71495
Unfortunately, the issue does not go away, even after reverting back
to slave-parallel-workers=0 in my.cnf, and restarting the mysql
instance.
Any quick idea, as to how we may get the
You can try these steps:
1-) Stop slave and write down the replication coordinates getting that in
MySQL's error log (*very important step*);
2-) Issue the `reset slave` command on MySQL Slave;
3-) Issue the CHANGE MASTER TO considering the replication coordinates
you've just written down on step
Ping !! :)
On Mon, Sep 1, 2014 at 8:27 AM, Ajay Garg ajaygargn...@gmail.com wrote:
Hi all.
We have replication set-up, where we cater to HUUGEE amounts of data.
Since quite some time, we have been facing issues wherein the slave
lags behind master quite a lot.
So, yesterday we were able
Thanks Akshay for the reply.
On Tue, Sep 2, 2014 at 12:25 PM, Akshay Suryavanshi
akshay.suryavansh...@gmail.com wrote:
Hello Ajay,
I tried testing the slave-parallel-workers few months ago, what I can surely
tell you its still under development, and at that time needed some critical
bug
Hi all.
We have replication set-up, where we cater to HUUGEE amounts of data.
Since quite some time, we have been facing issues wherein the slave
lags behind master quite a lot.
So, yesterday we were able to setup parallel replication, by
incorporating the following changes ::
a)
To begin
