MySQL Forums :: Replication :: Replication lag when no primary key on InnoDB


Advanced Search

Replication lag when no primary key on InnoDB
Posted by: Stéphane Brisson ()
Date: September 13, 2010 02:26PM

Hi,

Using:
mysql Ver 14.14 Distrib 5.1.49, for unknown-linux-gnu (x86_64) using readline 5.1


Deleting rows from a master is causing replication lag when there is no PRIMARY KEY on InnoDB table. When I delete a small subset ( < 500) , everything is fine (slave can handle it).

But when it's a massive delete, > 5000 rows, Seconds_Behind_Master keeps increasing... and slave thread seems to get stuck on 'Reading event from the relay log'.

I'm asking why it's taking so long. It's look like the thread is doing a full table scan on each row deletion because there's no primary key. Am I right ?

Was fine when it was in statement-based binary logging in 5.0.

Thanks

Stephan

Options: ReplyQuote


Subject Views Written By Posted
Replication lag when no primary key on InnoDB 4143 Stéphane Brisson 09/13/2010 02:26PM
Re: Replication lag when no primary key on InnoDB 1514 Rick James 09/14/2010 08:02PM
Re: Replication lag when no primary key on InnoDB 1030 Rick James 09/14/2010 08:05PM
Re: Replication lag when no primary key on InnoDB 1420 Stéphane Brisson 09/15/2010 01:38PM
Re: Replication lag when no primary key on InnoDB 1122 Rick James 09/15/2010 09:14PM
Re: Replication lag when no primary key on InnoDB 837 Stéphane Brisson 09/16/2010 06:54AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.