"Hannes Rohde" <[EMAIL PROTECTED]> wrote:
>
> innodb_data_file_path=ibdata1:2G:autoextend
>
> innodb_buffer_pool_size=1200M
> innodb_additional_mem_pool_size=20M
>
>
May not solve the replication issue, but if this is a 4GByte server that is
dedicated to MySQL (ie you aren't using memory for an
Hello.
The outputs of the following statements would be helpful, if you want that
somebody helps you:
SHOW MASTER STATUS;
SHOW SLAVE STATUS;
SHOW STATUS;
Execute them on the master and the slave.
"Hannes Rohde" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
>We use MySQL as a
ry your last paragraph's suggestion.
Thanks,
Hannes
-Ursprüngliche Nachricht-
Von: Marc Slemko [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 10. Februar 2005 11:24
An: Hannes Rohde
Cc: mysql@lists.mysql.com
Betreff: Re: Slow Replication
On Wed, 9 Feb 2005 22:07:19 +0100, Hannes R
On Wed, 9 Feb 2005 22:07:19 +0100, Hannes Rohde <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> We use MySQL as a database backend on a portal site. We have a two
> database server setup (one master, one slave). The master is a PIV 3,2 GHz.,
> 2 GB Ram and a 80GB Raid-1 system. The slave is a PIV
Jeremy Zawodny wrote:
< snip >
>
> Are subsequent inserts just as slow to replicate?
>
> Can you show us the output of SHOW SLAVE STATUS and maybe the my.cnf
> files of the master and a slow slave?
>
> Jeremy
>
Thanks for the response. Below is the info you requested. If there's
anything
On Wed, Sep 05, 2001 at 03:43:00PM -0500, Jeff Adams wrote:
> Greetings,
>
> This morning we sucessfully inserted a new record on our master
> MySQL machine. 4 1/2 hours later, the change showed up on the
> slaves. I was under the impression that MySQl replication would
> occur in a more timely f
