Merge lp:~hrvojem/percona-xtradb-cluster/rn-5.6.21-25.8 into lp:percona-xtradb-cluster

Proposed by Hrvoje Matijakovic on 2014-11-17
Status: Merged
Approved by: Hrvoje Matijakovic on 2014-11-25
Approved revision: 920
Merge reported by: Hrvoje Matijakovic
Merged at revision: not available
Proposed branch: lp:~hrvojem/percona-xtradb-cluster/rn-5.6.21-25.8
Merge into: lp:percona-xtradb-cluster
Diff against target: 308 lines (+157/-4)
9 files modified
doc-pxc/source/conf.py (+3/-2)
doc-pxc/source/howtos/cenots_howto.rst (+4/-0)
doc-pxc/source/installation.rst (+1/-1)
doc-pxc/source/manual/bootstrap.rst (+6/-0)
doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.21-25.8.rst (+70/-0)
doc-pxc/source/release-notes/release-notes_index.rst (+1/-0)
doc-pxc/source/wsrep-provider-index.rst (+45/-0)
doc-pxc/source/wsrep-status-index.rst (+26/-0)
doc-pxc/source/wsrep-system-index.rst (+1/-1)
To merge this branch: bzr merge lp:~hrvojem/percona-xtradb-cluster/rn-5.6.21-25.8
Reviewer Review Type Date Requested Status
Raghavendra D Prabhu 2014-11-17 Pending
Review via email: mp+242005@code.launchpad.net
To post a comment you must log in.

Looks good to me.

For https://github.com/codership/galera/issues/88

Bug fixed: Bootstrapping a node tried to resolve gcomm address list specified in
wsrep-cluster-address.

920. By Hrvoje Matijakovic on 2014-11-25

- Percona XtraDB Cluster 5.6.21-25.8 release notes
- Bugfix for Bug #1392369
- fixed missing wsrep status variables

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc-pxc/source/conf.py'
2--- doc-pxc/source/conf.py 2014-09-04 14:22:31 +0000
3+++ doc-pxc/source/conf.py 2014-11-25 13:29:06 +0000
4@@ -53,9 +53,9 @@
5 # built documents.
6 #
7 # The short X.Y version.
8-version = '5.6.20'
9+version = '5.6.21'
10 # The full version, including alpha/beta/rc tags.
11-release = '5.6.20-25.7'
12+release = '5.6.21-25.8'
13
14 # The language for content autogenerated by Sphinx. Refer to documentation
15 # for a list of supported languages.
16@@ -145,6 +145,7 @@
17 extlinks = {'bug': ('https://bugs.launchpad.net/percona-xtradb-cluster/+bug/%s',
18 '#'), 'mysqlbug': ('http://bugs.mysql.com/bug.php?id=%s',
19 '#'), 'githubbug': ('https://github.com/codership/galera/issues/%s',
20+ '#'), 'wsrepbug': ('https://github.com/codership/mysql-wsrep/issues/%s',
21 '#')}
22
23 # A list of ignored prefixes for module index sorting.
24
25=== modified file 'doc-pxc/source/howtos/cenots_howto.rst'
26--- doc-pxc/source/howtos/cenots_howto.rst 2014-01-29 15:10:12 +0000
27+++ doc-pxc/source/howtos/cenots_howto.rst 2014-11-25 13:29:06 +0000
28@@ -76,6 +76,10 @@
29 After this, first node can be started with the following command: ::
30
31 [root@percona1 ~]# /etc/init.d/mysql bootstrap-pxc
32+
33+In case you're running this tutorial on *CentOS* 7 server, systemd bootstrap service should be used instead: ::
34+
35+ [root@percona1 ~]# systemctl start mysql@bootstrap.service
36
37 This command will start the cluster with initial :variable:`wsrep_cluster_address` set to ``gcomm://``. This way the cluster will be bootstrapped and in case the node or |MySQL| have to be restarted later, there would be no need to change the configuration file.
38
39
40=== modified file 'doc-pxc/source/installation.rst'
41--- doc-pxc/source/installation.rst 2014-01-29 15:10:12 +0000
42+++ doc-pxc/source/installation.rst 2014-11-25 13:29:06 +0000
43@@ -9,7 +9,7 @@
44
45 Ready-to-use binaries are available from the *Percona XtraDB Cluster* `download page <http://www.percona.com/downloads/Percona-XtraDB-Cluster-56/>`_, including:
46
47- * ``RPM`` packages for *RHEL* 5 and *RHEL* 6
48+ * ``RPM`` packages for *RHEL* 5, *RHEL* 6, and *RHEL* 7
49
50 * *Debian* packages
51
52
53=== modified file 'doc-pxc/source/manual/bootstrap.rst'
54--- doc-pxc/source/manual/bootstrap.rst 2013-11-21 11:29:19 +0000
55+++ doc-pxc/source/manual/bootstrap.rst 2014-11-25 13:29:06 +0000
56@@ -32,6 +32,12 @@
57
58 /etc/init.d/mysql bootstrap-pxc
59
60+.. note::
61+
62+ On CentOS/RHEL 7 following bootstrap command should be used: ::
63+
64+ systemctl start mysql@bootstrap.service
65+
66 This way values in :file:`my.cnf` would remain unchanged. Next time node is restarted it won't require updating the configuration file. This can be useful in case cluster has been previously set up and for some reason all nodes went down and the cluster needs to be bootstrapped again.
67
68 Other Reading
69
70=== added file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.21-25.8.rst'
71--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.21-25.8.rst 1970-01-01 00:00:00 +0000
72+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.21-25.8.rst 2014-11-25 13:29:06 +0000
73@@ -0,0 +1,70 @@
74+.. rn:: 5.6.21-25.8
75+
76+======================================
77+ |Percona XtraDB Cluster| 5.6.21-25.8
78+======================================
79+
80+Percona is glad to announce the release of |Percona XtraDB Cluster| 5.6 on November 25th 2014. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster-56/release-5.6.21-25.8/>`_ or from our :doc:`software repositories </installation>`.
81+
82+Based on `Percona Server 5.6.21-70.1 <http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.21-70.1.html>`_ including all the bug fixes in it, `Galera Replicator 3.8 <https://github.com/codership/galera/milestones/3.8>`_ and on `Codership wsrep API 25.7 <https://launchpad.net/codership-mysql/+milestone/5.6.21-25.7>`_ is now the current **General Availability** release. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.6.21-25.8 milestone <https://launchpad.net/percona-xtradb-cluster/+milestone/5.6.21-25.8>`_ at Launchpad.
83+
84+New Features
85+============
86+
87+ Galera 3.8 introduces auto-eviction for nodes in the cluster experiencing network issues like packet loss. It is off by default and is turned on with :variable:`evs.auto_evict` option. This feature requires EVS protocol version (:variable:`evs.version`) ``1``. During the EVS protocol upgrade all membership changes are communicated over EVS protocol version ``0`` to preserve backwards compatibility, protocol is upgraded to the highest commonly supported version when forming a new group so if there exist a single node with older version in the group, the group protocol version remains as ``0`` and auto-eviction is not functional. (:bug:`1274192`).
88+
89+ |Percona XtraDB Cluster| now supports backup locks in XtraBackup SST (in the default ``xtrabackup-v2`` :variable:`wsrep_sst_method`). `Backup locks <http://www.percona.com/doc/percona-server/5.6/management/backup_locks.html>`_ are used in lieu of ``FLUSH TABLES WITH READ LOCK`` on the donor during SST. This should allow for minimal disruption of existing and incoming queries, even under high load. Thus, this should allow for even faster SST and node being in 'donor/desynced' state. This also introduces following constraints: |Percona XtraDB Cluster| 5.6.21 requires |Percona XtraBackup| 2.2.5 or higher; An older (< 5.6.21) joiner cannot SST from a newer (>= 5.6.21) donor. This is enforced through SST versioning (sent from joiner to donor during SST) and logged to error log explicitly. (:bug:`1390552`).
90+
91+ |Percona XtraDB Cluster| is now shipped with Galera MTR test suite.
92+
93+Bugs fixed
94+==========
95+
96+ |Percona XtraDB Cluster| now shows a warning in case additional utilities, like ``pv`` which may not affect critical path of SST, are not installed. Bug fixed :bug:`1248688`.
97+
98+ Fixed the ``UNIV_DEBUG`` build failures. Bug fixed :bug:`1384413`.
99+
100+ ``mysqldump`` SST can now use username/password from :variable:`wsrep_sst_auth` under group of ``[sst]`` in :file:`my.cnf` in order not to display the credentials in the error log. Bug fixed :bug:`1293798`.
101+
102+ Normal shutdown under load would cause server to remain hanging because replayer failed to finish. Bug fixed :bug:`1358701`.
103+
104+ :variable:`wsrep_causal_reads` variable was not honored when declared as global. Bug fixed :bug:`1361859`.
105+
106+ Assertion failure ``lock != ctx->wait_lock`` has been fixed. Bug fixed :bug:`1364840`.
107+
108+ ``garbd`` would not work when cluster address was specified without the port. Bug fixed :bug:`1365193`.
109+
110+ Fixed wsrep options compiler warnings in *Fedora* 20. Bug fixed :bug:`1369916`.
111+
112+ If ``mysqld`` gets killed during the SST it will leave an unclean data directory behind. This would cause |Percona XtraDB Cluster| to fail when the server would be started next time because the data directory would be corrupted. This was fixed by resuming the startup in case :variable:`wsrep-recover` failed to recover due to corrupted data directory. The old behavior is still achievable through :variable:`--exit-on-recover-fail` command line parameter to ``mysqld_safe`` or ``exit-on-recover-fail`` under ``[mysqld_safe]`` in :file:`my.cnf`. Bug fixed :bug:`1378578`.
113+
114+ |Percona XtraDB Cluster| now reads environment variables for mysqld from following files (if present): /etc/default/mysql in Debian/Ubuntu; ``/etc/sysconfig/mysql`` in CentOS 6 or lower; ``/etc/sysconfig/mysql`` in CentOS 7 with ``mysql.service``; ``/etc/sysconfig/XYZ`` in CentOS 7 with ``mysql@XYZ.service`` (``/etc/sysconfig/bootstrap`` is supplied by default). Bug fixed :bug:`1381492`.
115+
116+ ``gvwstate.dat`` file was removed on joiner when :ref:`xtrabackup_sst` method was used. Bug fixed :bug:`1388059`.
117+
118+ |Percona XtraDB Cluster| now detects older joiners which don't have the backup lock support. Bug fixed :bug:`1390552`.
119+
120+ Longer ``wsrep-recover`` is now handled gracefully in Debian init scripts rather than returning immediately with a false positive fail.
121+
122+ ``wsrep-recover`` log is now also written to mysql error log now.
123+
124+ Issue with stale PID files and Debian init script have been fixed now. It now emits a warning for stale PID files. 
125+
126+ :file:`sst_in_progress` file is not removed anymore in case of failed SST.
127+
128+ In case stored procedure containing a non-InnoDB statement (MyISAM) performed autocommit, that commit would be entered two times: at statement end and next time at stored procedure end. Bug fixed :wsrepbug:`2`.
129+
130+ TOI now skips replication if all tables are temporary. Bugs fixed :wsrepbug:`11` and :wsrepbug:`13`.
131+
132+ Two appliers conflicting with local transaction and resulting later in (acceptable) BF-BF lock conflict, would cause cluster to hang when the other BF thread would not grant the lock back after its local transaction got aborted. Bug fixed :wsrepbug:`7`.
133+
134+ Bootstrapping a node tried to resolve gcomm address list specified in :variable:`wsrep-cluster-address`. Bug fixed :githubbug:`88`.
135+
136+ ``xtrabackup-v2`` SST did not clean the undo log directory. Bug fixed :bug:`1394836`.
137+
138+ Inserts to a table with autoincrement primary key could result in duplicate key error if another node joined or dropped from the cluster during the insert processing. Bug fixed :bug:`1366997`.
139+
140+Other bugs fixed :bug:`1378138`, :bug:`1377226`, :bug:`1376965`, :bug:`1356859`, :bug:`1026181`, :bug:`1367173`, :bug:`1390482`, :bug:`1391634`, and :bug:`1392369`.
141+
142+Help us improve quality by reporting any bugs you encounter using our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_. As always, thanks for your continued support of Percona!
143+
144
145=== modified file 'doc-pxc/source/release-notes/release-notes_index.rst'
146--- doc-pxc/source/release-notes/release-notes_index.rst 2014-09-01 14:11:54 +0000
147+++ doc-pxc/source/release-notes/release-notes_index.rst 2014-11-25 13:29:06 +0000
148@@ -6,6 +6,7 @@
149 :maxdepth: 1
150 :glob:
151
152+ Percona-XtraDB-Cluster-5.6.21-25.8
153 Percona-XtraDB-Cluster-5.6.20-25.7
154 Percona-XtraDB-Cluster-5.6.19-25.6
155 Percona-XtraDB-Cluster-5.6.15-25.5
156
157=== modified file 'doc-pxc/source/wsrep-provider-index.rst'
158--- doc-pxc/source/wsrep-provider-index.rst 2014-07-18 11:33:37 +0000
159+++ doc-pxc/source/wsrep-provider-index.rst 2014-11-25 13:29:06 +0000
160@@ -50,6 +50,17 @@
161 :dyn: No
162 :default: no
163
164+.. variable:: evs.auto_evict
165+
166+ :version: Introduced in :rn:`5.6.21-25.8`
167+ :cli: Yes
168+ :conf: Yes
169+ :scope: Global
170+ :dyn: Yes
171+ :default: 0
172+
173+Number of entries allowed on delayed list until auto eviction takes place. Setting value to 0 disables auto eviction protocol on the node, though node response times will still be monitored. For auto eviction to be enabled requires EVS protocol version (:variable:`evs.version`) ``1``.
174+
175 .. variable:: evs.causal_keepalive_period
176
177 :cli: Yes
178@@ -70,6 +81,38 @@
179
180 This variable is used for EVS (Extended Virtual Synchrony) debugging it can be used only when :variable:`wsrep_debug` is set to ``ON``.
181
182+.. variable:: evs.delay_margin
183+
184+ :version: Introduced in :rn:`5.6.21-25.8`
185+ :cli: Yes
186+ :conf: Yes
187+ :scope: Global
188+ :dyn: Yes
189+ :default: PT1S
190+
191+Time period that a node can delay its response from expected until it is added to delayed list. The value must be higher than the highest RTT between nodes.
192+
193+.. variable:: evs.delayed_keep_period
194+
195+ :version: Introduced in :rn:`5.6.21-25.8`
196+ :cli: Yes
197+ :conf: Yes
198+ :scope: Global
199+ :dyn: Yes
200+ :default: PT30S
201+
202+Time period that node is required to remain responsive until one entry is removed from delayed list.
203+
204+.. variable:: evs.evict
205+
206+ :version: Introduced in :rn:`5.6.21-25.8`
207+ :cli: Yes
208+ :conf: Yes
209+ :scope: Global
210+ :dyn: Yes
211+
212+Manual eviction can be triggered by setting the :variable:`evs.evict` to a certain node value. Setting the :variable:`evs.evict` to an empty string will clear the evict list on the node where it was set.
213+
214 .. variable:: evs.inactive_check_period
215
216 :cli: Yes
217@@ -198,6 +241,8 @@
218 :dyn: No
219 :default: 0
220
221+This variable defines the EVS protocol version. Auto eviction is enabled when this variable is set to ``1``. Default 0 for backwards compatibility.
222+
223 .. variable:: evs.view_forget_timeout
224
225 :cli: Yes
226
227=== modified file 'doc-pxc/source/wsrep-status-index.rst'
228--- doc-pxc/source/wsrep-status-index.rst 2014-07-18 11:33:37 +0000
229+++ doc-pxc/source/wsrep-status-index.rst 2014-11-25 13:29:06 +0000
230@@ -26,12 +26,20 @@
231
232 .. variable:: wsrep_repl_keys
233
234+Total number of keys replicated.
235+
236 .. variable:: wsrep_repl_keys_bytes
237
238+Total size (in bytes) of keys replicated.
239+
240 .. variable:: wsrep_repl_data_bytes
241
242+Total size (in bytes) of data replicated.
243+
244 .. variable:: wsrep_repl_other_bytes
245
246+Total size of other bits replicated.
247+
248 .. variable:: wsrep_received
249
250 Total number of writesets received from other nodes.
251@@ -74,6 +82,8 @@
252
253 .. variable:: wsrep_flow_control_paused_ns
254
255+The total time spent in a paused state measured in nanoseconds.
256+
257 .. variable:: wsrep_flow_control_paused
258
259 Time since the last status query that replication was paused due to flow control.
260@@ -128,6 +138,8 @@
261
262 .. variable:: wsrep_cert_index_size
263
264+This variable shows the number of entries in the certification index.
265+
266 .. variable:: wsrep_causal_reads_
267
268 Shows the number of writesets processed while the variable :variable:`wsrep_causal_reads` was set to ``ON``.
269@@ -140,6 +152,18 @@
270
271 This status variable provides the information regarding the group communication replication latency. This latency is measured from the time point when a message is sent out to the time point when a message is received.
272
273+.. variable:: wsrep_evs_delayed
274+
275+List of UUIDs of the evicted nodes.
276+
277+.. variable:: wsrep_evs_evict_list
278+
279+Comma separated list of nodes that are considered delayed. The node format is ``<uuid>:<address>:<count>`` where ``<count>`` is the number of entries on delayed list for that node.
280+
281+.. variable:: wsrep_evs_state
282+
283+Internal EVS protocol state.
284+
285 .. variable:: wsrep_cluster_conf_id
286
287 Number of cluster membership changes happened.
288@@ -160,6 +184,8 @@
289 * ``Disconnected`` -
290
291 .. variable:: wsrep_connected
292+
293+This variable shows if the node is connected to the cluster. If the value is OFF, the node has not yet connected to any of the cluster components. This may be due to misconfiguration.
294
295 .. variable:: wsrep_local_bf_aborts
296
297
298=== modified file 'doc-pxc/source/wsrep-system-index.rst'
299--- doc-pxc/source/wsrep-system-index.rst 2014-09-01 14:11:54 +0000
300+++ doc-pxc/source/wsrep-system-index.rst 2014-11-25 13:29:06 +0000
301@@ -53,7 +53,7 @@
302 :cli: Yes
303 :conf: Yes
304 :scope: Global
305- :dyn: No
306+ :dyn: Yes
307
308 This minimally needs to be any single other cluster node's address that is alive and a member of the cluster. In practice, it is best (but not necessary) to provide a complete list of all possible cluster nodes.  This takes the form of: ::
309

Subscribers

People subscribed via source and target branches