Author: mcbrown
Date: 2007-08-04 07:41:27 +0200 (Sat, 04 Aug 2007)
New Revision: 7327
Log:
Committing some changes after Stefan's comments
Modified:
trunk/refman-5.0/ha.xml
Modified: trunk/refman-5.0/ha.xml
===================================================================
--- trunk/refman-5.0/ha.xml 2007-08-03 17:46:46 UTC (rev 7326)
+++ trunk/refman-5.0/ha.xml 2007-08-04 05:41:27 UTC (rev 7327)
Changed blocks: 7, Lines Added: 22, Lines Deleted: 67; 5486 bytes
@@ -97,31 +97,17 @@
<listitem>
<para>
There is no guarantee that data on master and slaves will be
- consistent.
-
- <remark>
- [SH] "... at a given point in time" I'd suggest to add.
- </remark>
+ consistent at a given point in time. Because replication is
+ asynchronous there may be a small delay between data being
+ written to the master and it being available on the slaves.
+ This can cause problems in applications where a write to the
+ master must be available for a read on the slaves (for
+ example a web application).
</para>
</listitem>
<listitem>
<para>
- Because replication is asynchronous there may be a small
- delay between data being written to the master and it being
- available on the slaves.
-
- <remark>
- [SH] This sounds like the previous item (no guarantee...).
- Also, the delay may be big if slaves attach to the network
- only from time to time (e.g. replicating to laptop
- computers).
- </remark>
- </para>
- </listitem>
-
- <listitem>
- <para>
<emphasis role="bold">Recommended uses</emphasis>
</para>
</listitem>
@@ -154,15 +140,11 @@
<listitem>
<para>
Offline backup. You can use replication to keep a copy of
- the data. You can take the slave down and get a reliable
- snapshot of the data (without MySQL running), then restart
- MySQL and replication to catch up.
-
- <remark>
- [SH] This doesn't make it clear if you're talking about
- the master or the slave (it's the master that needs to be
- stopped I guess).
- </remark>
+ the data. By replicating the data to a slave, you take the
+ slave down and get a reliable snapshot of the data (without
+ MySQL running), then restart MySQL and replication to catch
+ up. The master (and any other slaves) can be kept running
+ during this period.
</para>
</listitem>
@@ -352,16 +334,12 @@
<listitem>
<para>
- <emphasis>Heartbeat</emphasis> is not a data replication
- solution, but a solution for monitoring servers and switching
- active MySQL servers automatically in the event of failure.
- Heartbeat needs to be combined with MySQL Replication or DRBD to
- provide automatic failover.
-
- <remark>
- [SH] I'm still wondering what Heartbeat is - a third-party
- software?
- </remark>
+ <emphasis>Heartbeat</emphasis> is a third party software
+ solution for Linux. It is not a data replication or
+ synchronization solution, but a solution for monitoring servers
+ and switching active MySQL servers automatically in the event of
+ failure. Heartbeat needs to be combined with MySQL Replication
+ or DRBD to provide automatic failover.
</para>
</listitem>
@@ -400,13 +378,7 @@
<entry>No</entry>
</row>
<row>
- <entry>Automated database
-
- <remark>
- [SH] Or does that have to be "DB"?
- </remark>
-
- failover</entry>
+ <entry>Automated database failover</entry>
<entry>No</entry>
<entry>No</entry>
<entry>Yes</entry>
@@ -420,14 +392,7 @@
<entry>< 3 seconds</entry>
</row>
<row>
- <entry>Automatic resynchronization
-
- <remark>
- [SH] This was "auto resync" which sounded too geeky to me
- :-)
- </remark>
-
- of data</entry>
+ <entry>Automatic resynchronization of data</entry>
<entry>No</entry>
<entry>No</entry>
<entry>Yes</entry>
@@ -451,20 +416,14 @@
<entry>Yes</entry>
</row>
<row>
- <entry><remark>
- [SH] This could be misleading: read-intensive = for
- read-intensive uses, or rather the setup would be
- read-intensive? Same for the write-intensive below.
- </remark>
-
- Read-intensive</entry>
+ <entry>Supports Read-intensive applications</entry>
<entry>Yes</entry>
<entry>Yes</entry>
<entry>Yes, when combined with MySQL Replication</entry>
<entry>Yes</entry>
</row>
<row>
- <entry>Write-intensive</entry>
+ <entry>Supports Write-intensive applications</entry>
<entry>No</entry>
<entry>No</entry>
<entry>Yes</entry>
@@ -474,11 +433,7 @@
<entry>Maximum number of nodes per group</entry>
<entry>One master, multiple slaves</entry>
<entry>One master, multiple slaves</entry>
- <entry>One active (primary), multiple passive (secondary)
-
- <remark>
- [SH] I'm missing a noun here
- </remark></entry>
+ <entry>One active (primary), multiple passive (secondary) nodes</entry>
<entry>255</entry>
</row>
<row>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7327 - trunk/refman-5.0 | mcbrown | 4 Aug |
