List:Replication« Previous MessageNext Message »
From:Lasitha Alawatta Date:February 27 2008 9:25am
Subject:RE: MySQL replication delaying issue
View as plain text  
Hi Marcus,

 

 

Thank you very much for your comments. 

We are running with MySQL var.6. We are using MYISAM and InnoDB storage
engines. 

Also we have around 30 triggers (write data to log tables).

 

Best Regards,

Lasitha

 

 

From: Marcus Bointon [mailto:marcus@stripped] 
Sent: Tuesday, February 26, 2008 8:45 PM
To: Lasitha Alawatta
Cc: replication@stripped
Subject: Re: MySQL replication delaying issue

 

On 26 Feb 2008, at 16:28, Lasitha Alawatta wrote:





Server Environment :  Six identical Linux Enterprise version 4 running,
servers with having MySQL version 6.

we are using "MySQL multi-master replication" method for database
replication.

 

Are you really running 6? It's still very much an alpha. 5.0 is current,
5.1 is in release candidate stage.





There is a delay (5-7 minutes) of that data replication process.

We notice that it's because of MySQL table locking.

 

 

That's not specifically a replication issue, but it suggests you're
using MyISAM (or similar) tables that don't support row-level locking.
Switching to InnoDB should cure that.

 

Marcus

-- 

Marcus Bointon

Synchromedia Limited: Creators of http://www.smartmessages.net/

UK resellers of info@hand CRM solutions

marcus@stripped | http://www.synchromedia.co.uk/





 

DOTW DISCLAIMER:

This e-mail and any attachments are strictly confidential and intended for the addressee
only. If you are not the named addressee you must not disclose, copy or take
any action in reliance of this transmission and you should notify us as soon as possible.
If you have received it in error, please contact the message sender immediately.
This e-mail and any attachments are believed to be free from viruses but it is your
responsibility to carry out all necessary virus checks and DOTW accepts no liability
in connection therewith. 

This e-mail and all other electronic (including voice) communications from the sender's
company are for informational purposes only.  No such communication is intended
by the sender to constitute either an electronic record or an electronic signature or to
constitute any agreement by the sender to conduct a transaction by electronic means.

Attachment: [text/html]
Attachment: [text/html]
Attachment: [text/html]
Thread
MySQL replication delaying issueLasitha Alawatta26 Feb
  • Re: MySQL replication delaying issueMarcus Bointon26 Feb
  • RE: MySQL replication delaying issueRick James26 Feb
    • Re: MySQL replication delaying issueMarcus Bointon26 Feb
      • Re: MySQL replication delaying issueJed Reynolds26 Feb
        • Re: MySQL replication delaying issueMarcus Bointon26 Feb
          • RE: MySQL replication delaying issueRick James26 Feb
            • Re: MySQL replication delaying issueJed Reynolds26 Feb
        • Re: MySQL replication delaying issueEric Bergen26 Feb
  • Re: MySQL replication delaying issueJed Reynolds26 Feb
    • RE: MySQL replication delaying issueRick James26 Feb
  • RE: MySQL replication delaying issueLasitha Alawatta27 Feb