bk commit - mysqldoc tree (jon:1.2792)

[jon]

Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2792 05/03/31 23:30:19 jon@stripped +1 -0
  NDB doesn't support repeatable reads, so restoring 
  from backup isn't "hot" (per Salle). 

  Docs/manual.texi
    1.2624 05/03/31 23:30:14 jon@stripped +11 -3
    NDB doesn't support repeatable reads, so restoring 
    from backup isn't "hot" (per Salle). 

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	jon
# Host:	gigan.site
# Root:	/home/jon/bk/mysqldoc

--- 1.2623/Docs/manual.texi	2005-03-31 23:03:12 +10:00
+++ 1.2624/Docs/manual.texi	2005-03-31 23:30:14 +10:00
@@ -75128,6 +75128,13 @@
 there is enough memory allocated for the backup. Also check that there is enough
 space on the hard drive partition of the backup target.
 
+Currently (as of MySQL 4.1.10a) NDB does not support repeatable reads, which can
+cause problems with the restore process. While the backup process is "hot",
+restoring a MySQL Cluster from backup is not a 100% "hot" process. This is due
+to the fact that, for the duration of the restore process, running transactions
+get non-repeatable reads from the restored data. This means that the state of
+the data is inconsistent while the restore is in progress.
+
 @c  TODO: Either write some additional material for this section, or fold it
 @c  into another section.
 
@@ -75592,8 +75599,8 @@
 
 @item @strong{Performance and limitation-related issues}:
   @itemize @asis
-  @item The query cache disabled since it is not invalidated if an update occurs
-  on a different MySQL server
+  @item The query cache is disabled, since it is not invalidated if an update occurs
+  on a different MySQL server.
   @item There are query performance issues due to sequential access to the NDB
   storage engine; it is also relatively more expensive to do many range scans
   than it is with either MyISAM or InnoDB.
@@ -75608,7 +75615,8 @@
   @itemize @asis
   @item The only supported isolation level is @code{READ_COMMITTED}. (InnoDB
   supports @code{READ_COMMITTED}, @code{REPEATABLE_READ}, and
-  @code{SERIALIZABLE}.)
+  @code{SERIALIZABLE}.) See @uref{MySQL Cluster Backup Troubleshooting} for
+  informaiton on how this can effect backup/restore of Cluster databases.
   @item No durable commits on disk. Commits are replicated, but there is no
   guarantee that logs are flushed to disk on commit.
   @end itemize