Yup; that's the ideal way for WAN based replication .. But for LAN;
there is no point other than adding extra overhead
--
Thanks
Venu
Sent from iPhone
On Jan 25, 2010, at 11:47 AM, Alex Yurchenko > wrote:
On Mon, 25 Jan 2010 10:47:23 -0800, Jeremy Zawodny
wrote:
If the connection between
On Mon, Jan 25, 2010 at 11:47 AM, Alex Yurchenko <
alexey.yurche...@codership.com> wrote:
> On Mon, 25 Jan 2010 10:47:23 -0800, Jeremy Zawodny
> wrote:
> > If the connection between a slave and master is interrupted, the slave
> > won't
> > report itself as being "behind" until the slave's networ
On Mon, 25 Jan 2010 10:47:23 -0800, Jeremy Zawodny
wrote:
> If the connection between a slave and master is interrupted, the slave
> won't
> report itself as being "behind" until the slave's network timeout to the
> master expires and it reconnect (assuming it can).
>
> Jeremy
Hi Jeremy,
Does i
On Jan 25, 2010, at 12:44 PM, Jeremy Zawodny wrote:
+1 on a replication heartbeat w/configurable heartbeat time. We'd
want to issue a heartbeat pules every 1 sec in our environment to
measure *true* replication latency.
Jeremy
This is in MySQL 5.5 already. See MASTER_HEARTBEAT_PERIOD at
If the connection between a slave and master is interrupted, the slave won't
report itself as being "behind" until the slave's network timeout to the
master expires and it reconnect (assuming it can).
Jeremy
On Mon, Jan 25, 2010 at 10:44 AM, wrote:
> Hi Jeremy,
>
> Thanks for the input. I'm not
Hi Jeremy,
Thanks for the input. I'm not sure what you mean with true replication
latency here.
Anyway, the replication system can internally measure latencies
from the point where the replication event was passed for replication
until it was received/applied in the receiving end. And these laten
+1 on a replication heartbeat w/configurable heartbeat time. We'd want to
issue a heartbeat pules every 1 sec in our environment to measure *true*
replication latency.
Jeremy
On Fri, Jan 22, 2010 at 6:21 AM, Kristian Nielsen
wrote:
> The three companies Continuent, Codership, and Monty Program
On Mon, 25 Jan 2010 13:55:44 +0100, Kristian Nielsen
wrote:
>
> I think it would be useful if you explained what the problems are with
that
> interface, in your opinion.
>
Let me start with that I'm not that much familiar with the current MySQL
replication code and may not be qualified to judge
Alex Yurchenko writes:
> On Fri, 22 Jan 2010 21:14:29 +0100, Kristian Nielsen
> wrote:
>> http://forge.mysql.com/wiki/ReplicationFeatures/ReplicationInterface
> U. I am of rather poor opinion of that interface. It is not breaking
> with bad traditions at all. I'm not sure if it is high
9 matches
Mail list logo
