Merge lp:~hrvojem/percona-server/bug955266-5.5 into lp:percona-server/5.5

Proposed by Hrvoje Matijakovic on 2012-03-27
Status: Merged
Approved by: Alexey Kopytov on 2012-03-27
Approved revision: 228
Merged at revision: 229
Proposed branch: lp:~hrvojem/percona-server/bug955266-5.5
Merge into: lp:percona-server/5.5
Diff against target: 76 lines (+23/-4)
2 files modified
doc/source/management/innodb_lru_dump_restore.rst (+21/-2)
doc/source/release-notes/Percona-Server-5.5.16-22.0.rst (+2/-2)
To merge this branch: bzr merge lp:~hrvojem/percona-server/bug955266-5.5
Reviewer Review Type Date Requested Status
Alexey Kopytov (community) 2012-03-27 Approve on 2012-03-27
Review via email: mp+99520@code.launchpad.net
To post a comment you must log in.
Alexey Kopytov (akopytov) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/management/innodb_lru_dump_restore.rst'
2--- doc/source/management/innodb_lru_dump_restore.rst 2012-03-16 10:41:48 +0000
3+++ doc/source/management/innodb_lru_dump_restore.rst 2012-03-27 13:30:23 +0000
4@@ -19,7 +19,6 @@
5
6 After finishing the restore operation, the thread switches into dump mode, to periodically dump the LRU. The period is specified by the configuration variable's value in seconds. For example, if you set the variable to 60, then the thread saves the LRU list once per minute.
7
8-
9 Manual Operation
10 ================
11
12@@ -91,7 +90,6 @@
13
14 The requested number of pages is the number of pages that were in the LRU dump file. A page might not be read if it is already in the buffer pool, or for some other miscellaneous reasons, so the number of pages read can be less than the number requested.
15
16-
17 Implementation Details
18 ======================
19
20@@ -102,6 +100,12 @@
21 The dump file is not deleted after loading, so you should delete it if you wish to disable the feature. For example, suppose you dump the LRU, and then some time later you decide to enable automatic dumping and reloading. You set the configuration variable and restart |MySQL|. Upon restart, the server will load the LRU to its state in the previously saved file, which might be very stale and not what you want to happen.
22
23
24+Block Startup until LRU dump is loaded
25+=======================================
26+
27+|Percona Server| provides a boolean option to block the start of XtraDB until LRU is preloaded from dump. When the variable :variable:`innodb_blocking_buffer_pool_restore` is set to ON, XtraDB waits until the restore of the dump is completed before reporting successful startup to the server. This variable is OFF by default.
28+
29+
30 Version Specific Information
31 ============================
32
33@@ -129,6 +133,21 @@
34
35 This variable was renamed to :variable:`innodb_buffer_pool_restore_at_startup`, beginning in release 5.5.10-20.1. It still exists as :variable:`innodb_auto_lru_dump` in versions prior to that.
36
37+
38+.. variable:: innodb_blocking_buffer_pool_restore
39+
40+ :version 5.5.16-22.0: Added
41+ :cli: Yes
42+ :conf: Yes
43+ :scope: Global
44+ :dyn: No
45+ :vartype: Boolean
46+ :default: OFF
47+ :range: ON/OFF
48+
49+When this variable is set to ON XtraDB waits until the restore of the dump is completed before reporting successful startup to the server.
50+
51+
52 .. variable:: innodb_buffer_pool_restore_at_startup
53
54 :version 5.5.10-20.1: Added.
55
56=== modified file 'doc/source/release-notes/Percona-Server-5.5.16-22.0.rst'
57--- doc/source/release-notes/Percona-Server-5.5.16-22.0.rst 2011-10-24 11:15:33 +0000
58+++ doc/source/release-notes/Percona-Server-5.5.16-22.0.rst 2012-03-27 13:30:23 +0000
59@@ -18,7 +18,7 @@
60
61 Using this approach, support for Fake Changes have been implemented in order to remove the overhead and make it faster.
62
63-By reading the rows for “INSERT“, “UPDATE“ and “DELETE“ statements but not updating them (Fake Changes), the rollback is very fast as in most cases there is nothing to do.
64+By reading the rows for "INSERT", "UPDATE" and "DELETE" statements but not updating them (Fake Changes), the rollback is very fast as in most cases there is nothing to do.
65
66 Kill Idle Transactions
67 ----------------------
68@@ -30,7 +30,7 @@
69 Block Startup until LRU dump is loaded
70 --------------------------------------
71
72-Added a new boolean option, :variable:`innodb-blocking-buffer-pool-restore`, which is ``OFF`` by default. When set to ``ON``, restoring from the LRU dump file is synchronous, i.e. |XtraDB| waits until it is complete before reporting successful startup to the server. Bug Fixed: :bug:`785489` (*Alexey Kopytov*).
73+Added a new boolean option, :variable:`innodb_blocking_buffer_pool_restore`, which is ``OFF`` by default. When set to ``ON``, restoring from the LRU dump file is synchronous, i.e. |XtraDB| waits until it is complete before reporting successful startup to the server. Bug Fixed: :bug:`785489` (*Alexey Kopytov*).
74
75 Behavior changes
76 ----------------

Subscribers

People subscribed via source and target branches