[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql-internals
Subject:    Re: Internal log syncronization (InnoDB and Replication)...
From:       "Heikki Tuuri" <Heikki.Tuuri () innodb ! com>
Date:       2002-09-30 22:39:32
[Download RAW message or body]

Jeremy,

----- Original Message -----
From: "Jeremy Zawodny" <Jeremy@Zawodny.com>
To: "Heikki Tuuri" <Heikki.Tuuri@innodb.com>
Cc: "Peter Zaitsev" <peter@mysql.com>; <internals@lists.mysql.com>;
<monty@mysql.com>
Sent: Tuesday, October 01, 2002 1:20 AM
Subject: Re: Internal log syncronization (InnoDB and Replication)...


> On Mon, Sep 30, 2002 at 11:49:13PM +0300, Heikki Tuuri wrote:
> >
> > There could be a my.cnf parameter
> >
> > flush_binlog_at_trx_commit=...
...

> Right.  The best solution, I think is to use 1.  If performance is an
> issue, look for a hardware solution.  We've begun using hardware RAID
> with NVRAM write caches so that the disk writes don't hurt as much
> (during short periods of high activitiy, at least).
>
> > Similarly, the slaves should be banned from reading the binlog ahead
> > of the last point where we know the binlog is flushed to disk.
> >
> > Thus, with respect to 'durability' in the whole master-slave setup,
> > the transaction commit would happen at the time the master binlog is
> > flushed to disk.
>
> Yes, that would be very helpful.  It's better to have a slave that
> might be *slightly* behind than one that is out of sync with the
> master.  Depending how it became out of sync, it could be very
> difficult to detect.

I think this is something for the replication developer of MySQL AB in 2003
or 2004 :).

> Jeremy

Heikki



> Jeremy D. Zawodny     |  Perl, Web, MySQL, Linux Magazine, Yahoo!
> <Jeremy@Zawodny.com>  |  http://jeremy.zawodny.com/
>
> MySQL 3.23.51: up 55 days, processed 1,156,083,155 queries (240/sec. avg)



---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail internals-thread4851@lists.mysql.com
To unsubscribe, e-mail <internals-unsubscribe@lists.mysql.com>

[prev in list] [next in list] [prev in thread] [next in thread]