On 2/26/2019 1:57 PM, Jim wrote:
On 2/26/2019 9:44 AM, shawn l.green wrote:
Hello Jim,
On 2/25/2019 7:29 PM, Jim wrote:
On 2/25/2019 5:46 PM, shawn l.green wrote:
Hello Jim,
On 2/25/2019 5:04 PM, Jim wrote:
I have a question about mysql replication. I believe I understand
most
On 2/26/2019 9:44 AM, shawn l.green wrote:
Hello Jim,
On 2/25/2019 7:29 PM, Jim wrote:
On 2/25/2019 5:46 PM, shawn l.green wrote:
Hello Jim,
On 2/25/2019 5:04 PM, Jim wrote:
I have a question about mysql replication. I believe I understand most
of it, but have a question about user
Hello Jim,
On 2/25/2019 7:29 PM, Jim wrote:
On 2/25/2019 5:46 PM, shawn l.green wrote:
Hello Jim,
On 2/25/2019 5:04 PM, Jim wrote:
I have a question about mysql replication. I believe I understand most
of it, but have a question about user privileges.
I understand on the master
On 2/25/2019 5:46 PM, shawn l.green wrote:
Hello Jim,
On 2/25/2019 5:04 PM, Jim wrote:
I have a question about mysql replication. I believe I understand most
of it, but have a question about user privileges.
I understand on the master, the replication user must have the
Repl_slave_priv
Hello Jim,
On 2/25/2019 5:04 PM, Jim wrote:
I have a question about mysql replication. I believe I understand most
of it, but have a question about user privileges.
I understand on the master, the replication user must have the
Repl_slave_priv privilege as described here:
https://dev.mysql.com
I have a question about mysql replication. I believe I understand most
of it, but have a question about user privileges.
I understand on the master, the replication user must have the
Repl_slave_priv privilege as described here:
https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html
Hi Guys
I am once again having a weird issue... well weird to me anyway.
We have a master,slave setup using mysql 5.7 and they are both
connected on the same network segment through the same switch.
During the weekend a HUGE amount of processing was done on the master,
and thus
On 7/6/2015 1:39 PM, Claudio Nanni wrote:
Hi Jatin,
Say if i am using a DB instance for quiet some time on node-1 and
it has data in it. If i decide to have replication with another DB
instance , will all the data from node-1 be first replicated to
node-2's DB ? Or will it just
Hi All
We are basically intending to implement High Availability for our
application. In this regard , we want to use Mysql replication for this
purpose.
We would have a two-node cluster , say node-1 node-2.
Assume that if node-1is functioning we want the DB changes on it to be
replicated
On 7/5/2015 10:48 PM, Claudio Nanni wrote:
Hello Jatin,
We are basically intending to implement High Availability for our
application. In this regard , we want to use Mysql replication for
this purpose.
Your scenario(MySQL Master/Slave with Failover/Failback procedures)
has been a typical
From: Walter Heck walterh...@olindata.com
Subject: Re: Which replication solution should I choose?
Hi Johan,
it'll be a good ol' war story of the transition of a large 130k QPS MMM
cluster
to PXC, so come visit for sure. Here's the link to the session:
http://www.percona.com/live/london
Hi,
Is that a way to make multi-master asynchronous replication with mysql ou
external lib?
I know galera cluster but it is synchronous.
The problem is a set of eventually disconected nodes need to send all changes
(when connected) to a master always connected node.
Thanks!
Rodrigo
- Original Message -
From: Rodrigo Ferreira rodrigof_si...@yahoo.com
Subject: Multi-Master Asynchronous Replication
Hi,
Is that a way to make multi-master asynchronous replication with mysql ou
external lib?
I know galera cluster but it is synchronous.
The problem is a set
Thanks for your response.
In this case, circular replication is not apropriate because there are about 10
to 15 nodes, and it is known that availability decreases on circular setup as
the number of nodes increases.
Another reason (related to availability) is that nodes are eventually
Sorry, I will check this = with recent MariaDB, a slave can have multiple
masters
On Monday, November 24, 2014 2:26 PM, Rodrigo Ferreira
rodrigof_si...@yahoo.com wrote:
Thanks for your response.
In this case, circular replication is not apropriate because there are about 10
to 15
- Original Message -
From: Walter Heck walterh...@olindata.com
Subject: Re: Which replication solution should I choose?
If you happen to be at the Percona Live conference next week in London I'm
speaking about Galera in a high performance setup as well.
Ooo, very interested
at 11:39 AM, Johan De Meersman vegiv...@tuxera.be
wrote:
- Original Message -
From: Walter Heck walterh...@olindata.com
Subject: Re: Which replication solution should I choose?
If you happen to be at the Percona Live conference next week in London
I'm
speaking about Galera
Hi All :)
I am creating an environment based on about 15 hardware nodes. 6 of them
will be for mysql databases. They will be divided into three pairs (3x2
nodes). Nodes in every pair will be configured with replication.
I done similar configuration about an year ago. I used than:
- percona 5.5
with replication.
I done similar configuration about an year ago. I used than:
- percona 5.5 with standard asynchronous replication;
- Multi Master Replication Manager for MySQL (http://mysql-mmm.org/
https://t.yesware.com/tl/2627942011ccc3835f76c6e9ba4c0af91f3d3722/407ea34fcfb29332bbc93cdb34f13e4f
. They will be divided into three pairs (3x2
nodes). Nodes in every pair will be configured with replication.
I done similar configuration about an year ago. I used than:
- percona 5.5 with standard asynchronous replication;
- Multi Master Replication Manager for MySQL (http://mysql-mmm.org/
https
Hi Rafal,
On Wed, Oct 29, 2014 at 3:16 PM, Rafał Radecki radecki.ra...@gmail.com
wrote:
Thanks for the info, Walter.
I checked some basic info about Galera and it looks very promising. Can
you tell what is preferable for loadbalancing of requests? HAProxy/Galera
loadbalancer or maybe
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 error log (*very important step*);
2-) Issue
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
+replication up and
running (even with the plain old non-multi-threaded mode)?
On Tue, Sep 2, 2014 at 12:57 PM, Ajay Garg ajaygargn...@gmail.com wrote:
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
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
needs to go through lot
of testing. Please share your observation and findings in case it differs
from the above.
Cheers!!!
Akshay
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
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
On 8/29/2014 7:40 PM, Suresh Kuna wrote:
You can paste the show slave status\G here for us to review and on Master,
show global variables like 'log-bin%'; show master status ( 3 to 4 times
continuously )
Master:
+--+--+--+--+
| File
, is the Exec_Master_Log_Pos incrementing or not?
Not - see prior post
3-) Why are you reconfiguring all the replication just because the link
went down?
AFAIK, I am no reconfiguring, after the link comes back up, the
slave does not start replicating - sometimes. Happens quite
infrequently
On 8/29/2014 7:40 PM, Suresh Kuna wrote:
You can paste the show slave status\G here for us to review and on Master,
show global variables like 'log-bin%'; show master status ( 3 to 4 times
continuously )
after a more complex transaction;
There's a duplicate key on the audit table, 18699. Delete it and restart
slave (start slave). Check slave status again, might be more rows in there
duplicated.
You might want to compare the row to master to ensure it's a duplicate
before deleting from slave.
On Aug 30, 2014 7:52 AM, william
On 8/29/2014 7:40 PM, Suresh Kuna wrote:
You can paste the show slave status\G here for us to review and on Master,
show global variables like 'log-bin%'; show master status ( 3 to 4 times
continuously ) global var, below
+--+--+--+--+
|
Based on the SHOW SLAVE STATUS output you've sent us, I'd suggest that you
check what the application is doing, understand *why* the application is
violating the PK of the table information_server.audit, repair the possible
application problem and the, reconfigure the replication.
It seems
On 30/08/14 09:39, william drescher wrote:
On 8/29/2014 7:40 PM, Suresh Kuna wrote:
You can paste the show slave status\G here for us to review and on
Master,
show global variables like 'log-bin%'; show master status ( 3 to 4 times
continuously )
Master:
On 8/29/2014 7:40 PM, Suresh Kuna wrote:
You can paste the show slave status\G here for us to review and on Master,
show global variables like 'log-bin%'; show master status ( 3 to 4 times
continuously )
mysql show global variables like 'log_bin%';
+-+---+
Thanks for pointing out the importance of the last error
I resynced the slave to the master, reset the master position,
and restarted the slave.
Now all works fine and I am much better equipped next time to
debug the loss of the link.
When is the Last Error data deleted from the show slave
On 30/08/14 12:56, william drescher wrote:
Thanks for pointing out the importance of the last error
I resynced the slave to the master, reset the master position, and
restarted the slave.
Now all works fine and I am much better equipped next time to debug the
loss of the link.
When is the
On 8/30/2014 12:53 PM, Jose Julian Buda wrote:
On 30/08/14 12:56, william drescher wrote:
Thanks for pointing out the importance of the last error
I resynced the slave to the master, reset the master position, and
restarted the slave.
Now all works fine and I am much better equipped next
Replication novice
I have a master server at the office and a replication server at
home. This setup has been working for a couple of years.
Occasionally the replication server gets out of sync (usually
following a internet problem and the vpn going down.)
I just stop the slave, make sure
Whilst there are a few possibilities, check on the master that your binary
logs are being written to. Another possible reason could be filtering.
On 29 Aug 2014 21:36, william drescher will...@techservsys.com wrote:
Replication novice
I have a master server at the office and a replication
Hello guys, some points to check here:
1-) Is the master server configured with sync_binlog=1 ?
2-) About the SHOW SLAVE STATUS output, when slave seems to be just reading
events from master, is the Exec_Master_Log_Pos incrementing or not?
3-) Why are you reconfiguring all the replication just
-) Is the master server configured with sync_binlog=1 ?
2-) About the SHOW SLAVE STATUS output, when slave seems to be just reading
events from master, is the Exec_Master_Log_Pos incrementing or not?
3-) Why are you reconfiguring all the replication just because the link
went down?
Cheers,
--
*WB
Hi all,
I need to configure fan-in replication from MySQL DB shards into single
MySQL DB.
All shards and fan-in replica are located on separate physical servers.
All table IDs are unique across all shards.
Is there way to do this.
I have considered Tungsten, but it seems like it can't
Hello Neubyr,
On 1/29/2014 7:16 PM, neubyr wrote:
I am trying to understand MySQL statement based replication with LOAD DATA
LOCAL INFILE statement'.
According to manual -
https://dev.mysql.com/doc/refman/5.0/en/replication-features-load.html -
LOAD DATA LOCAL INFILE is replicated as LOAD DATA
Thanks for the details Shawn.
So row based replication would avoid server side LOAD DATA on slave.
Unfortunately, the Master is using MySQL ver 5.0, so I don't think it can
use row based replication.
- thanks,
N
On Thu, Jan 30, 2014 at 7:48 AM, shawn l.green shawn.l.gr...@oracle.comwrote
I am trying to understand MySQL statement based replication with LOAD DATA
LOCAL INFILE statement'.
According to manual -
https://dev.mysql.com/doc/refman/5.0/en/replication-features-load.html -
LOAD DATA LOCAL INFILE is replicated as LOAD DATA LOCAL INFILE, however, I
am seeing it replicated
If I don't mistake, there are some parameters to make that you are saying.
Check statement-based-replication and row-based-replication. I think that
this could help you.
Regards,
Antonio.
2014/1/17 Richard Reina gatorre...@gmail.com
I have 3 relay MySQL database servers on my small office LAN backing up a
master and 3 more machines backing up each relay (1 each). They are all
replicating all databases and all tables. The master although running fine
is almost eight years old.
Manuel,
Thank you very much for this information. This sounds like a very good
strategy. I think I will try switching some slaves from one relay to another to
familiarize myself and get practice and them do it to deploy a new master.
Again, thank you very much.
Richard
El Jan 18, 2014, a
I have 3 relay MySQL database servers on my small office LAN backing up a
master and 3 more machines backing up each relay (1 each). They are all
replicating all databases and all tables. The master although running fine
is almost eight years old. I'm thinking it's probably time to make one of
the
Am 17.01.2014 22:42, schrieb Richard Reina:
I have 3 relay MySQL database servers on my small office LAN backing up a
master and 3 more machines backing up each relay (1 each). They are all
replicating all databases and all tables. The master although running fine
is almost eight years old.
Hi!
Ed == Ed L mysql@bluepolka.net writes:
Ed Mysql newbie here, looking for some help configuring 5.0.45 master-slave
Ed replication. Here's my scenario...
Ed We have a heavily loaded 30gb 5.0.45 DB we need to replicate via
Ed master-slave configuration to a new, beefier server
Mysql newbie here, looking for some help configuring 5.0.45 master-slave
replication. Here's my scenario...
We have a heavily loaded 30gb 5.0.45 DB we need to replicate via
master-slave configuration to a new, beefier server running same mysql
5.0.45, and then cutover to the new server
replication. Here's my scenario...
We have a heavily loaded 30gb 5.0.45 DB we need to replicate via
master-slave configuration to a new, beefier server running same mysql
5.0.45, and then cutover to the new server. Due to extreme SAN congestion
and a grossly overloaded master server, our DB dumps
@bluepolka.net
mailto:mysql@bluepolka.net wrote:
Mysql newbie here, looking for some help configuring 5.0.45
master-slave replication. Here's my scenario...
We have a heavily loaded 30gb 5.0.45 DB we need to replicate via
master-slave configuration to a new, beefier server running same mysql
master-slave
replication. Here's my scenario...
We have a heavily loaded 30gb 5.0.45 DB we need to replicate via
master-slave configuration to a new, beefier server running same mysql
5.0.45, and then cutover to the new server. Due to extreme SAN congestion
and a grossly overloaded master
On 24/07/2013 19:52, Rick James wrote:
4) 3 tables from the slaves are to be replicated back to the master
NO.
However, consider Percona XtraDb Cluster or MariaDB+Galera. They allow
multiple writable masters. But they won't let you be so selective about tables
not being replicated.
Here
I have been asked to set up multiple database replication which I have
done before for simple cases however there are some nuances with this
instance that add some complexity and I'd like to hear your collective
expertise on this proposed scenario:-
1) Single master database
2) n (probably 3
://mysql.rjweb.org/doc.php/galera
If you can live with them (plus replicating everything), it may be best for you.
-Original Message-
From: rich gray [mailto:r...@richgray.com]
Sent: Wednesday, July 24, 2013 8:21 AM
To: mysql@lists.mysql.com
Subject: Replication question
I have been
Hi,
I have configured replication from EC2 mysql instance to another mysql
instance on our network via vpn in between. Sometimes it is showing no
errors on the slave but the slave falls behind . When I issue the commands
stop slave ; start slave ; it again catches up with the master.
What
I've noticed a weird issue in our chained replication environment where when
setting user-defined variables, the first time the variable is used in a
session the value is NULL, but all uses thereafter work correctly.
The environment is such: we have a master (master1), which has a slave which
Hi Matthew,
On 16/07/2013 21:21, Matthew Ward wrote:
I've noticed a weird issue in our chained replication environment where when
setting user-defined variables, the first time the variable is used in a
session the value is NULL, but all uses thereafter work correctly.
snip
The first time I
that mysqldump in the future
slaves. Take a look at the first lines of the mysqldump where you'll find
the position and logfile those slaves need to start the replication from.
You can also use xtrabackup if you like.
Manuel.
--
MySQL General Mailing List
For list archives: http
:
Enable log-slave-updates in the slave you want to be a master.
Do a mysqldump -e --master-data=2 and put that mysqldump in the future
slaves. Take a look at the first lines of the mysqldump where you'll find
the position and logfile those slaves need to start the replication from.
You
at the first lines of the mysqldump where you'll find
the position and logfile those slaves need to start the replication from.
You can also use xtrabackup if you like.
Manuel.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com
If you're able to use MySQL 5.6 and enable GTIDs then it gets a whole lot
simpler as you don't need to worry about finding the correct positions in the
binary logs. Take a look at
http://www.mysql.com/why-mysql/white-papers/mysql-replication-high-availability/
and http://www.mysql.com/why
for replication to catchup everywhere.
3. FLUSH LOGS everywhere.
4. Now CHANGE MASTER on the Slave to the start (POS=0 or 4) of the freshly
created binlog in the machine that is the Slave's new Master.
5. Start writes.
-Original Message-
From: Richard Reina [mailto:gatorre...@gmail.com
slaves need to start the replication from.
You can also use xtrabackup if you like.
Manuel.
to notice is 'operating on' in the text you quoted. If you
limit execution of those DDL statements to just a few databases, then
any user with enough privileges that start the DDL command from the
context of the permitted database will be able to affect those objects
on the slave via replication
Hello Dimitre,
On 3/24/2013 5:23 PM, Radoulov, Dimitre wrote:
Hi all,
we need to move a few databases from one host to another.
During the process we need to use replication filters (to replicate
only the databases to be moved).
The current MySQL version is 5.5, the new one will be 5.6.
We're
Hi all,
we need to move a few databases from one host to another.
During the process we need to use replication filters (to replicate
only the databases to be moved).
The current MySQL version is 5.5, the new one will be 5.6.
We're using mixed binlog_format.
We're planing to use:
replicate-wild
I have used debug on monitor and agent:
- on agent I see:
/etc/init.d/mysql-mmm-agent start
Starting MMM Agent Daemon: 2013/03/13 16:19:52 DEBUG Created pid file
'/var/run/mysql-mmm/mmm_agentd.pid' with pid 13640
2013/03/13 16:19:52 DEBUG Listener: Waiting for connection...
2013/03/13 16:19:53
Hi All.
I use:
cat /etc/redhat-release
CentOS release 6.3 (Final)
uname -a
Linux prod1.local 2.6.32-279.14.1.el6.x86_64 #1 SMP Tue Nov 6 23:43:09
UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
on db host:
rpm -qa | grep mmm
mysql-mmm-2.2.1-1.el6.noarch
bmysql-mmm-agent-2.2.1-1.el6.noarch
on monitor
2013/3/11 Rafał Radecki radecki.ra...@gmail.com
Hi All.
I use:
cat /etc/redhat-release
CentOS release 6.3 (Final)
uname -a
Linux prod1.local 2.6.32-279.14.1.el6.x86_64 #1 SMP Tue Nov 6 23:43:09
UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
on db host:
rpm -qa | grep mmm
Hi,
I think MMM's proper functionality depends a lot on network interface
configuration and sometimes it behaves odd. I moved to MySQL or in my
case to MariaDB + Galera + HaProxy configuration. It's not difficult to
setup. There is no SPO as in case with monitor host in MMM, much more
robust
HI Trimurthy,
Just curious won't it make that data inconsistent on the slave?
Thanks
On Fri, Feb 22, 2013 at 12:15 AM, Trimurthy trimur...@tulassi.com wrote:
Dear Mike Franon,
i have also faced the same problem while setting up the replication. by
that time i have added the error
So I created a new test box on AWS, and just did one upgrade from
5.0.96 to 5.1, like I did before and replication will not work from a
master with 5.0.96 to a slave with 5.1.68
I keep getting Error 1062, Duplicate Entry for key
I get no errors when I do a mysql_upgrade, all comes back ok.
I
update the master ASAP in a short timeframe too
and re-init replication if needed
normally both should have exactly the same version
the slaves must be updated first because otherwise
a master may write instructions in the binlog the older
slave does not undersatdn at all, but as said normally
,
just not the other way around?
Thanks
On Thu, Feb 21, 2013 at 1:03 PM, Reindl Harald h.rei...@thelounge.net wrote:
update the master ASAP in a short timeframe too
and re-init replication if needed
normally both should have exactly the same version
the slaves must be updated first because
of 100 fixes are replication bugs
On Thu, Feb 21, 2013 at 1:03 PM, Reindl Harald h.rei...@thelounge.net wrote:
update the master ASAP in a short timeframe too
and re-init replication if needed
normally both should have exactly the same version
the slaves must be updated first because
It is safer to have the Slave be a newer version.
-Original Message-
From: Reindl Harald [mailto:h.rei...@thelounge.net]
Sent: Thursday, February 21, 2013 10:30 AM
To: mysql@lists.mysql.com
Subject: Re: replication fails after upgrade to 5.6
Am 21.02.2013 19:11, schrieb Mike
@lists.mysql.com
Subject: Re: replication fails after upgrade to 5.6
Am 21.02.2013 19:11, schrieb Mike Franon:
Is the only way to really fix this is to upgrade master? I thought
you can replicate from master - slave if version is higher on slave,
just not the other way around?
normally no
but take
Am 20.02.2013 23:27, schrieb Mike Franon:
So I successfully upgraded a test db server from 5.0.96 all the way up to 5.6
Replication as the slave, where the master is 5.0.96, started working
for about 10 minutes and then got the following error:
[ERROR] Slave SQL: Error 'Duplicate entry
Replication as the slave, where the master is 5.0.96, started working
for about 10 minutes and then got the following error:
[ERROR] Slave SQL: Error 'Duplicate entry 'data' for key 'PRIMARY'' on
query. Default database: 'test'. Query: 'UPDATE IGNORE , Error_code:
1062
All of our other slaves
So I successfully upgraded a test db server from 5.0.96 all the way up to 5.6
Replication as the slave, where the master is 5.0.96, started working
for about 10 minutes and then got the following error:
[ERROR] Slave SQL: Error 'Duplicate entry 'data' for key 'PRIMARY'' on
query. Default
2013/2/14 Robert Citek robert.ci...@gmail.com
According to the client, nothing is writing to the slave and
everything is being logged at the master. I have not had the
opportunity to independently verified any of this, yet. I do know
that the slave is not in read-only mode, but rather we
, 2013 2:59 PM
To: Rick James
Cc: mysql
Subject: Re: slave replication with lots of 'duplicate entry' errors
On Thu, Feb 14, 2013 at 5:46 PM, Rick James rja...@yahoo-inc.com
wrote:
Is it in read only mode?
Furthermore, are all users logging in as non-SUPER users? Note:
root bypasses
replication with lots of 'duplicate entry' errors
2013/2/13 Robert Citek robert.ci...@gmail.com
On Wed, Feb 13, 2013 at 8:59 AM, Robert Citek
robert.ci...@gmail.com
wrote:
Any other possibilities? Do other scenarios become likely if there
are two or more tables?
Of those
...@gmail.com
wrote:
Any other possibilities? Do other scenarios become likely if there
are two or more tables?
Of those, which are the most likely?
[from off-list responder]:
Other possibility: The replication is reading from master not from the
point when the dump was done
On Thu, Feb 14, 2013 at 5:46 PM, Rick James rja...@yahoo-inc.com wrote:
Is it in read only mode?
Furthermore, are all users logging in as non-SUPER users? Note: root
bypasses the readonly flag!
No. The user that is commonly used does have Super privileges. I am
not sure why, but it does.
?
Of those, which are the most likely?
[from off-list responder]:
Other possibility: The replication is reading from master not from the
point when the dump was done, but some time before and is fetching insert
statements which are already in the dump.
To prevent that I used
Yes. Except for a handful of static MyISAM tables. But the tables
that are experiencing the issues are all InnoDB and large (a dozen or
so fields, but lots of records.)
Regards,
- Robert
On Thu, Feb 14, 2013 at 5:59 PM, Singer Wang w...@singerwang.com wrote:
Are you using all InnoDB?
S
--
possibility: The replication is reading from master not from the
point when the dump was done, but some time before and is fetching insert
statements which are already in the dump.
To prevent that I used the coordinates in the dump file included with
--master-data=2. Could the coordinates
Agreed. Will do that along with several other possible changes. But
for the moment, I'm still gathering information and coming up with
plausible models.
Will also be turning on general mysql logging on both Master and
Slave, at least briefly, to see what statements are being run on both.
On Wed, Feb 13, 2013 at 8:59 AM, Robert Citek robert.ci...@gmail.com wrote:
Any other possibilities? Do other scenarios become likely if there
are two or more tables?
Of those, which are the most likely?
[from off-list responder]:
Other possibility: The replication is reading from master
Hi all.
I have installed a setup in which I use semisync replication. On master I have:
mysql show status like '%rpl%';
++-+
| Variable_name | Value
- Original Message -
From: Rafał Radecki radecki.ra...@gmail.com
Seconds_Behind_Master: 364
So if I have rpl_semi_sync_master_timeout=5000 (5s) and semisync
why is it possible on the slave to fall behind the master?
Semi-sync only guarantees that the slave has *received* the
Hi all.
I would like to clear values off Rpl_semi_sync_master_no_tx and
Rpl_semi_sync_master_no_times status variables because I am plugging a
sync replication setup into nagios.
I've tried:
mysql SET global Rpl_semi_sync_master_no_tx=0;
ERROR 1193 (HY000): Unknown system variable
- Original Message -
From: Néstor rot...@gmail.com
I spoke to soon!!!
Here is the error about 1.5 hours after replication has started.
121205 16:39:51 [ERROR] Slave: Error 'Duplicate entry '3468897'
for
Yes, that's what you get for running SQL_SLAVE_SKIP_COUNTER
1 - 100 of 3720 matches
Mail list logo
