Merge lp:~hrvojem/percona-xtradb-cluster/bug1319708-5.6 into lp:percona-xtradb-cluster

Proposed by Hrvoje Matijakovic on 2014-06-05
Status: Merged
Approved by: Raghavendra D Prabhu on 2014-07-18
Approved revision: no longer in the source branch.
Merge reported by: Hrvoje Matijakovic
Merged at revision: not available
Proposed branch: lp:~hrvojem/percona-xtradb-cluster/bug1319708-5.6
Merge into: lp:percona-xtradb-cluster
Diff against target: 386 lines (+181/-19)
13 files modified
.bzrignore (+1/-0)
doc-pxc/source/conf.py (+3/-4)
doc-pxc/source/glossary.rst (+1/-1)
doc-pxc/source/howtos/virt_sandbox.rst (+1/-1)
doc-pxc/source/installation/apt_repo.rst (+17/-6)
doc-pxc/source/intro.rst (+1/-1)
doc-pxc/source/manual/state_snapshot_transfer.rst (+1/-1)
doc-pxc/source/manual/xtrabackup_sst.rst (+2/-2)
doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.19-25.6.rst (+106/-0)
doc-pxc/source/release-notes/release-notes_index.rst (+1/-0)
doc-pxc/source/wsrep-provider-index.rst (+10/-0)
doc-pxc/source/wsrep-status-index.rst (+4/-0)
doc-pxc/source/wsrep-system-index.rst (+33/-3)
To merge this branch: bzr merge lp:~hrvojem/percona-xtradb-cluster/bug1319708-5.6
Reviewer Review Type Date Requested Status
Raghavendra D Prabhu (community) 2014-06-05 Approve on 2014-07-18
Review via email: mp+222237@code.launchpad.net
To post a comment you must log in.

In-line comments added.

review: Needs Fixing

lp:1280896 and lp:1260713 are two important bugs to be added as they are fixed.

lp:1260713 specifically introduces two new variables - wsrep_slave_FK_checks and wsrep_slave_UK_checks which are set to TRUE and FALSE respectively by default. They control whether FK and UK checking is done for applier threads.

Noted in in-line diff comments. Also, note that new variables added will need to be documented under variables.

review: Needs Fixing

Added inline diff comments.

review: Needs Fixing

Looks good.

review: Approve
777. By Hrvoje Matijakovic on 2014-07-18

- Bug fix for Bug #1319708
- Percona-XtraDB-Cluster-5.6.19-25.6 release notes

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file '.bzrignore'
2--- .bzrignore 2014-07-02 10:52:20 +0000
3+++ .bzrignore 2014-07-18 11:34:40 +0000
4@@ -3147,3 +3147,4 @@
5 storage/perfschema/gen_pfs_lex_token
6 sql/share/bulgarian
7 doc/build
8+doc-pxc/build/
9
10=== modified file 'doc-pxc/source/conf.py'
11--- doc-pxc/source/conf.py 2014-03-20 09:43:39 +0000
12+++ doc-pxc/source/conf.py 2014-07-18 11:34:40 +0000
13@@ -53,9 +53,9 @@
14 # built documents.
15 #
16 # The short X.Y version.
17-version = '5.6.15'
18+version = '5.6.19'
19 # The full version, including alpha/beta/rc tags.
20-release = '5.6.15-25.5'
21+release = '5.6.19-25.6'
22
23 # The language for content autogenerated by Sphinx. Refer to documentation
24 # for a list of supported languages.
25@@ -136,8 +136,6 @@
26
27 .. |Drizzle| replace:: *Drizzle*
28
29-.. |MariaDB| replace:: *MariaDB*
30-
31 .. |tar4ibd| replace:: :program:`tar4ibd`
32
33 .. |tar| replace:: :program:`tar`
34@@ -146,6 +144,7 @@
35
36 extlinks = {'bug': ('https://bugs.launchpad.net/percona-xtradb-cluster/+bug/%s',
37 '#'), 'mysqlbug': ('http://bugs.mysql.com/bug.php?id=%s',
38+ '#'), 'githubbug': ('https://github.com/codership/galera/issues/%s',
39 '#')}
40
41 # A list of ignored prefixes for module index sorting.
42
43=== modified file 'doc-pxc/source/glossary.rst'
44--- doc-pxc/source/glossary.rst 2013-09-05 13:37:01 +0000
45+++ doc-pxc/source/glossary.rst 2014-07-18 11:34:40 +0000
46@@ -32,7 +32,7 @@
47 *Percona XtraBackup* is an open-source hot backup utility for |MySQL| - based servers that doesn’t lock your database during the backup.
48
49 XtraDB
50- *Percona XtraDB* is an enhanced version of the InnoDB storage engine, designed to better scale on modern hardware, and including a variety of other features useful in high performance environments. It is fully backwards compatible, and so can be used as a drop-in replacement for standard InnoDB. More information `here <http://www.percona.com/docs/wiki/Percona-XtraDB:start>`_ .
51+ *Percona XtraDB* is an enhanced version of the InnoDB storage engine, designed to better scale on modern hardware, and including a variety of other features useful in high performance environments. It is fully backwards compatible, and so can be used as a drop-in replacement for standard InnoDB. More information `here <http://www.percona.com/doc/percona-server/5.5/percona_xtradb.html>`_ .
52
53 XtraDB Cluster
54 *Percona XtraDB Cluster* is a high availability solution for MySQL.
55
56=== modified file 'doc-pxc/source/howtos/virt_sandbox.rst'
57--- doc-pxc/source/howtos/virt_sandbox.rst 2013-09-05 13:37:01 +0000
58+++ doc-pxc/source/howtos/virt_sandbox.rst 2014-07-18 11:34:40 +0000
59@@ -7,7 +7,7 @@
60
61 The client node will have HAProxy installed and it will redirect requests to |PXC| nodes. This approach works well in real-world scenarios too. Running HAProxy on the application servers instead of having them as dedicated entities gives you benefits like no need for an extra network roundtrip, because loadbalancer and scalability of |PXC|'s load balancing layer scales simply with application servers.
62
63-We'll use `Percona <http://www.percona.com/docs/wiki/repositories:yum>`_ and `EPEL <http://fedoraproject.org/wiki/EPEL>`_ repositories for software installation.
64+We'll use `Percona <http://www.percona.com/doc/percona-xtradb-cluster/5.6/installation/yum_repo.html>`_ and `EPEL <http://fedoraproject.org/wiki/EPEL>`_ repositories for software installation.
65
66 After configuring the repositories you'll be able to install software that will be used. First, install |PXC| on the database nodes. ::
67
68
69=== modified file 'doc-pxc/source/installation/apt_repo.rst'
70--- doc-pxc/source/installation/apt_repo.rst 2014-01-29 15:10:12 +0000
71+++ doc-pxc/source/installation/apt_repo.rst 2014-07-18 11:34:40 +0000
72@@ -37,13 +37,12 @@
73
74 * 10.04LTS lucid
75 * 12.04LTS precise
76- * 12.10 quantal
77- * 13.04 raring
78 * 13.10 saucy
79-
80-
81-Install XtraDB Cluster
82-=======================
83+ * 14.04LTS trusty
84+
85+
86+Install Percona XtraDB Cluster
87+==============================
88
89 Make sure to remove existing |Percona XtraDB Cluster| 5.5 and |Percona Server| 5.5/5.6 packages before proceeding.
90
91@@ -64,3 +63,15 @@
92
93 deb http://repo.percona.com/apt VERSION main experimental
94 deb-src http://repo.percona.com/apt VERSION main experimental
95+
96+Apt-Pinning the packages
97+========================
98+
99+In some cases you might need to "pin" the selected packages to avoid the upgrades from the distribution repositories. You'll need to make a new file :file:`/etc/apt/preferences.d/00percona.pref` and add the following lines in it: ::
100+
101+ Package: *
102+ Pin: release o=Percona Development Team
103+ Pin-Priority: 1001
104+
105+For more information about the pinning you can check the official `debian wiki <http://wiki.debian.org/AptPreferences>`_.
106+
107
108=== modified file 'doc-pxc/source/intro.rst'
109--- doc-pxc/source/intro.rst 2014-03-20 09:43:39 +0000
110+++ doc-pxc/source/intro.rst 2014-07-18 11:34:40 +0000
111@@ -54,7 +54,7 @@
112 It uses the `Galera library <https://launchpad.net/galera>`_, version 3.x,
113 a generic Synchronous Multi-Master replication plugin for transactional applications.
114
115-Galera library is developed by `Codership Oy <http://www.codership.com/>`_.
116+Galera library is developed by `Codership Oy <http://www.galeracluster.com/>`_.
117
118 Galera 3.x supports such new features as:
119 * Incremental State Transfer (|IST|), especially useful for WAN deployments,
120
121=== modified file 'doc-pxc/source/manual/state_snapshot_transfer.rst'
122--- doc-pxc/source/manual/state_snapshot_transfer.rst 2014-01-30 13:56:19 +0000
123+++ doc-pxc/source/manual/state_snapshot_transfer.rst 2014-07-18 11:34:40 +0000
124@@ -39,5 +39,5 @@
125 Other Reading
126 =============
127
128-* `SST Methods for MySQL <http://www.codership.com/wiki/doku.php?id=sst_mysql>`_
129+* `SST Methods for MySQL <http://galeracluster.com/documentation-webpages/statetransfer.html#state-snapshot-transfer-sst>`_
130 * :ref:`Xtrabackup SST configuration<xtrabackup_sst>`
131
132=== modified file 'doc-pxc/source/manual/xtrabackup_sst.rst'
133--- doc-pxc/source/manual/xtrabackup_sst.rst 2014-03-20 13:08:06 +0000
134+++ doc-pxc/source/manual/xtrabackup_sst.rst 2014-07-18 11:34:40 +0000
135@@ -79,7 +79,7 @@
136
137 * OpenSSL based encryption with ``encrypt=2``. Socat must be built with openSSL for encryption: ``socat -V | grep OPENSSL``.
138
139- * Support for SSL encryption for just the key and crt files as implemented in `Galera <http://www.codership.com/wiki/doku.php?id=ssl_support>`_ can be enabled with ``encrypt=3`` option. Information on this option can be found :ref:`here <galera_sst_encryption>`.
140+ * Support for SSL encryption for just the key and crt files as implemented in `Galera <http://galeracluster.com/documentation-webpages/ssl.html?highlight=ssl#enabling-ssl>`_ can be enabled with ``encrypt=3`` option. Information on this option can be found :ref:`here <galera_sst_encryption>`.
141
142 Refer to this :ref:`document <xtrabackup_sst_encryption>` when enabling with ``encrypt=1``.
143
144@@ -215,7 +215,7 @@
145 Galera compatible encryption
146 ----------------------------
147
148-Support for SSL encryption for just the key and crt files as implemented in `Galera <http://www.codership.com/wiki/doku.php?id=ssl_support>`_ can be enabled with ``encrypt=3`` option. This has been implemented in :rn:`5.5.34-23.7.6` for compatibility with Galera. **NOTE**: This option does not provide certificate validation. In order to work correctly paths to the key and cert files need to be specified as well, like: ::
149+Support for SSL encryption for just the key and crt files as implemented in `Galera <http://galeracluster.com/documentation-webpages/ssl.html?highlight=ssl#enabling-ssl>`_ can be enabled with ``encrypt=3`` option. This has been implemented in :rn:`5.5.34-23.7.6` for compatibility with Galera. **NOTE**: This option does not provide certificate validation. In order to work correctly paths to the key and cert files need to be specified as well, like: ::
150
151 [sst]
152 encrypt=3
153
154=== added file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.19-25.6.rst'
155--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.19-25.6.rst 1970-01-01 00:00:00 +0000
156+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.19-25.6.rst 2014-07-18 11:34:40 +0000
157@@ -0,0 +1,106 @@
158+.. rn:: 5.6.17-25.6
159+
160+======================================
161+ |Percona XtraDB Cluster| 5.6.19-25.6
162+======================================
163+
164+Percona is glad to announce the release of |Percona XtraDB Cluster| 5.6 on July 21st 2014. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster-56/release-5.6.19-25.6/>`_ or from our :doc:`software repositories </installation>`.
165+
166+Based on `Percona Server 5.6.19-67.0 <http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.19-67.0.html>`_ including all the bug fixes in it, `Galera Replicator 3.6 <https://github.com/codership/galera/issues?milestone=1&page=1&state=closed>`_ and on `Codership wsrep API 25.6 <https://launchpad.net/wsrep-group/+milestone/5.6.19-25.6>`_ 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.19-25.6 milestone <https://launchpad.net/percona-xtradb-cluster/+milestone/5.6.19-25.6>`_ at Launchpad.
167+
168+New Features
169+============
170+
171+ During joiner joining the group, state message exchange provides us with ``gcache seqno limits``. That info is now used to choose a donor through IST first, if not possible, only then SST is attempted. :variable:`wsrep_sst_donor` is also honored here. This is also segment aware. (:bug:`1252461`)
172+
173+ Asynchronous replication slave thread is stopped when the node tries to apply next replication event while the node is in non-primary state. But it would then remain stopped after node successfully re-joined the cluster. A new variable :variable:`wsrep_restart_slave` has been implemented, which controls if |MySQL| slave should be restarted automatically when the node joins back to the cluster. (:bug:`1288479`)
174+
175+ Handling install message and install state message processing has been improved to make group forming more stable in case many nodes are joining the cluster. (:githubbug:`14`)
176+
177+ |Percona XtraDB Cluster| now supports storing the Primary Component state to disk by setting the :variable:`pc.recovery` variable to ``true``. The Primary Component can then recover automatically when all nodes that were part of the last saved state reestablish communications with each other. This feature can be used for automatic recovery from full cluster crashes, such as in the case of a data center power outage and graceful full cluster restarts without the need for explicitly bootstrapping a new Primary Component. (:githubbug:`10`)
178+
179+ New :variable:`wsrep_evs_repl_latency` status variable has been implemented which provides the group communication replication latency information. (:githubbug:`15`)
180+
181+ Node consistency issues with foreign keys have been fixed. This fix introduces two new variables: :variable:`wsrep_slave_FK_checks` and :variable:`wsrep_slave_UK_checks`. These variables are set to ``TRUE`` and ``FALSE`` respectively by default. They control whether Foreign Key and Unique Key checking is done for applier threads. (:bug:`1260713`).
182+
183+Bugs fixed
184+==========
185+
186+ Fixed the race condition in Foreign Key processing that could cause assertion. Bug fixed :bug:`1342959`.
187+
188+ The restart sequence in ``scripts/mysql.server`` would fail to capture and return if the start call failed to start the server, so a restart could occur that failed upon start-up, and the script would still return ``0`` as if it worked without any issues. Bug fixed :bug:`1339894`.
189+
190+ Updating a unique key value could cause server hang if slave node has enabled parallel slaves. Bug fixed :bug:`1280896`.
191+
192+ |Percona XtraDB Cluster| has implemented threadpool scheduling fixes. Bug fixed :bug:`1333348`.
193+
194+ ``garbd`` was returning incorrect return code, ie. when ``garbd`` was already started, return code was ``0``. Bug fixed :bug:`1308103`.
195+
196+ :variable:`wsrep_sst_rsync` would silently fail on joiner when ``rsync`` server port was already taken. Bug fixed :bug:`1099783`.
197+
198+ Example ``wsrep_notify`` script failed on node shutdown. Bug fixed :bug:`1132955`.
199+
200+ When :variable:`gmcast.listen_addr` was configured to a certain address, local connection point for outgoing connections was not bound to listen address. This would happen if OS has multiple interfaces with IP addresses in the same subnet, it may happen that OS would pick wrong IP for local connection point and other nodes would see connections originating from IP address which was not listened to. Bug fixed :bug:`1240964`.
201+
202+ Issue with re-setting galera provider (in :variable:`wsrep_provider_options`) has been fixed. Bug fixed :bug:`1260283`.
203+
204+ Variable :variable:`wsrep_provider_options` couldn't be set in runtime if no provider was loaded. Bug fixed :bug:`1260290`.
205+
206+ |Percona XtraDB Cluster| couldn't be built with *Bison* 3.0. Bug fixed :bug:`1262439`.
207+
208+ ``mysqld`` wasn't handling exceeding max writeset size wsrep error correctly. Bug fixed :bug:`1270920`.
209+
210+ When ``FLUSH TABLES WITH READ LOCK`` was used on a node with :variable:`wsrep_causal_reads` set to ``1`` while there was a ``DML`` on other nodes then, subsequent SELECTs/SHOW STATUS didn't hang earlier providing non-causal output, that has been fixed here. Bug fixed :bug:`1271177`.
211+
212+ Lowest group communication layer (evs) would fail to handle the situation properly when big number of nodes would suddenly start to see each other. Bugs fixed :bug:`1271918` and :bug:`1249805`.
213+
214+ |Percona XtraDB Cluster| server package no longer conflicts with ``mysql-libs`` package from *CentOS* repository. Bug fixed :bug:`1278516`.
215+
216+ The mysql-debug ``UNIV_DEBUG`` binary was missing from RPM/DEB server packages. Bug fixed :bug:`1290087`.
217+
218+ XtraBackup SST would fail if `progress <http://www.percona.com/doc/percona-xtradb-cluster/5.6/manual/xtrabackup_sst.html#progress>`_ option was used with large number of files. Bug fixed :bug:`1294431`.
219+
220+ When Query Cache was used and a node would go into non-PRIM state, queries which returned results earlier (and cached into query cache) would still return results whereas newer queries (or the ones not cached) would return ``unknown command``. Bug fixed :bug:`1296403`.
221+
222+ Brute Force abort did not work with INSERTs to table with single unique key. Bug fixed :bug:`1299116`.
223+
224+ |InnoDB| buffer pool dump and load was not working as expected due to :variable:`wsrep_recover` overwriting the buffer pool dump file. Bug fixed :bug:`1305955`.
225+
226+ Close referenced table opened in the same function when foreign constraints were checked, otherwise it could lead to server stall when running ``DROP TABLE``. Bug fixed :bug:`1309241`.
227+
228+ Compiling on *FreeBSD* 10.0 with ``CLANG`` would result in fatal error. Bug fixed :bug:`1309507`.
229+
230+ Truncating the sorted version of multi-byte character conversion could lead to wsrep certification failures. Bug fixed :bug:`1314854`.
231+
232+ Cluster node acting as async slave would stop with the wrong position after hitting :variable:`max_write_set_size`. Bug fixed :bug:`1309669`.
233+
234+ Fixed the events replication inconsistencies. Bug fixed :bug:`1312618`.
235+
236+ :variable:`wsrep_slave_threads` was counted towards :variable:`max_connections` which could cause ``ERROR 1040 (HY000): Too many connections`` error. Bug fixed :bug:`1315588`.
237+
238+ Leaving node was not set nonoperational if processed leave message originated from different view than the current one which could cause other nodes to crash. Bug fixed :bug:`1323412` (:githubbug:`41`).
239+
240+ ``garb`` couldn't be started with ``init`` script on *RHEL* 6.5. Bug fixed :bug:`1323652`.
241+
242+ SST would fail when binlogs were in dedicated directory that's located inside ``datadir``. This bug was a regression introduced by bug fix for :bug:`1273368`. Bug fixed :bug:`1326012`.
243+
244+ GTID of TOI operations is now also synced to |InnoDB| tablespace in order to get consistent backups. Bug fixed :bug:`1329055`.
245+
246+ ``mysql-debug`` is now distributed with binary ``tar.gz`` along with RPM and DEB packages. Bug fixed :bug:`1332073`.
247+
248+ Startup failure with ``Undetected state gap`` has been fixed. Bug fixed :bug:`1334606`.
249+
250+ Galera3 is now installed in ``/usr/lib/galera3/libgalera_smm.so`` with a compatibility symlink to ``/usr/lib/libgalera_smm.so``. Bug fixed :bug:`1279328`.
251+
252+ Galera could not be compiled on PowerPC. Bug fixed :githubbug:`59`.
253+
254+ Cluster could stall if leaving node failed to acknowledge all messages it had received due to exception and remaining nodes failed to reach consensus because of that. Bug fixed :githubbug:`37`.
255+
256+ When two node instances were set up on the same server with the two different IPs, they couldn't not work well because they were use wrong IP addresses. Bug fixed :githubbug:`31`.
257+
258+ Automated donor selection with segments gave inconsistent results. Bug fixed :githubbug:`29`.
259+
260+Other bug fixes: :bug:`1297822`, :bug:`1269811`, :bug:`1262887`, :bug:`1244835`, :bug:`1338995`, :githubbug:`11`, :githubbug:`40`, :githubbug:`38`, :githubbug:`33`, and :githubbug:`24`.
261+
262+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!
263+
264
265=== modified file 'doc-pxc/source/release-notes/release-notes_index.rst'
266--- doc-pxc/source/release-notes/release-notes_index.rst 2014-03-20 09:43:39 +0000
267+++ doc-pxc/source/release-notes/release-notes_index.rst 2014-07-18 11:34:40 +0000
268@@ -6,6 +6,7 @@
269 :maxdepth: 1
270 :glob:
271
272+ Percona-XtraDB-Cluster-5.6.19-25.6
273 Percona-XtraDB-Cluster-5.6.15-25.5
274 Percona-XtraDB-Cluster-5.6.15-25.4
275 Percona-XtraDB-Cluster-5.6.15-25.3
276
277=== modified file 'doc-pxc/source/wsrep-provider-index.rst'
278--- doc-pxc/source/wsrep-provider-index.rst 2014-03-20 09:43:39 +0000
279+++ doc-pxc/source/wsrep-provider-index.rst 2014-07-18 11:34:40 +0000
280@@ -485,6 +485,16 @@
281
282 When this variable is set to ``TRUE`` more recent primary component overrides older ones in case of conflicting prims.
283
284+.. variable:: pc.recovery
285+
286+ :cli: Yes
287+ :conf: Yes
288+ :scope: Global
289+ :dyn: No
290+ :default: true
291+
292+When this variable is set to ``true`` the node stores the Primary Component state to disk. The Primary Component can then recover automatically when all nodes that were part of the last saved state re-establish communications with each other. This feature allows automatic recovery from full cluster crashes, such as in the case of a data center power outage and graceful full cluster restarts without the need for explicitly bootstrapping a new Primary Component.
293+
294 .. variable:: pc.version
295
296 :cli: Yes
297
298=== modified file 'doc-pxc/source/wsrep-status-index.rst'
299--- doc-pxc/source/wsrep-status-index.rst 2014-01-29 15:10:12 +0000
300+++ doc-pxc/source/wsrep-status-index.rst 2014-07-18 11:34:40 +0000
301@@ -135,6 +135,10 @@
302 .. variable:: wsrep_incoming_addresses
303
304 Shows the comma-separated list of incoming node addresses in the cluster.
305+
306+.. variable:: wsrep_evs_repl_latency
307+
308+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.
309
310 .. variable:: wsrep_cluster_conf_id
311
312
313=== modified file 'doc-pxc/source/wsrep-system-index.rst'
314--- doc-pxc/source/wsrep-system-index.rst 2014-03-20 12:59:52 +0000
315+++ doc-pxc/source/wsrep-system-index.rst 2014-07-18 11:34:40 +0000
316@@ -231,7 +231,7 @@
317 :scope: Global
318 :dyn: Yes
319
320-This variable is used to set the notification `command <http://www.codership.com/wiki/doku.php?id=notification_command>`_ that server will execute every time cluster membership or local node status changes.
321+This variable is used to set the notification `command <http://galeracluster.com/documentation-webpages/notification-cmd.html>`_ that server will execute every time cluster membership or local node status changes.
322
323 .. variable:: wsrep_on
324
325@@ -309,6 +309,16 @@
326
327 This variable controls if *MyISAM* will be replicated or not. *MyISAM* replication is still experimental and that is one of the reasons why this variable is set to ``OFF`` by default.
328
329+.. variable:: wsrep_restart_slave
330+
331+ :cli: Yes
332+ :conf: Yes
333+ :scope: Global
334+ :dyn: Yes
335+ :default: OFF
336+
337+This variable controls if |MySQL| slave should be restarted automatically, when node joins back to cluster, because asynchronous replication slave thread is stopped when the node tries to apply next replication event while the node is in non-primary state.
338+
339 .. variable:: wsrep_retry_autocommit
340
341 :cli: Yes
342@@ -319,6 +329,26 @@
343
344 This variable sets the number of times autocommitted transactions will be tried in the cluster if it encounters certification errors. In case there is a conflict, it should be safe for the cluster node to simply retry the statement without the client's knowledge with the hopes that it will pass the next time. This can be useful to help an application using autocommit to avoid the deadlock errors that can be triggered by replication conflicts. If this variable is set to ``0`` transaction won't be retried and if it is set to ``1`` it will be retried once.
345
346+.. variable:: wsrep_slave_FK_checks
347+
348+ :cli: Yes
349+ :conf: Yes
350+ :scope: Global
351+ :dyn: Yes
352+ :default: ON
353+
354+This variable is used to control if Foreign Key checking is done for applier threads.
355+
356+.. variable:: wsrep_slave_UK_checks
357+
358+ :cli: Yes
359+ :conf: Yes
360+ :scope: Global
361+ :dyn: Yes
362+ :default: OFF
363+
364+This variable is used to control if Unique Key checking is done for applier threads.
365+
366 .. variable:: wsrep_slave_threads
367
368 :cli: Yes
369@@ -327,7 +357,7 @@
370 :dyn: Yes
371 :default: 1
372
373-This variable controls the number of threads that can apply replication transactions in parallel. Galera supports true parallel replication, replication that applies transactions in parallel only when it is safe to do so. The variable is dynamic, you can increase/decrease it anytime, note that, when you decrease it, it won't kill the threads immediately but stop them after they are done applying current transaction (the effect with increase is immediate though). If any replication consistency problems are encountered, it's recommended to set this back to ``1`` to see if that resolves the issue. The default value can be increased for better throughput. You may want to increase it many a time as suggested `in Codership documentation <http://www.codership.com/wiki/doku.php?id=flow_control>`_, in JOINED state for instance to speed up the catchup process to SYNCED. You can also estimate the optimal value for this from :variable:`wsrep_cert_deps_distance` as suggested `on this page <http://www.codership.com/wiki/doku.php?id=monitoring#checking_replication_health>`_. You can also refer to `this <http://www.codership.com/wiki/doku.php?id=configuration_tips#parallel_applying_wsrep_slave_threads>`_ for more configuration tips.
374+This variable controls the number of threads that can apply replication transactions in parallel. Galera supports true parallel replication, replication that applies transactions in parallel only when it is safe to do so. The variable is dynamic, you can increase/decrease it anytime, note that, when you decrease it, it won't kill the threads immediately but stop them after they are done applying current transaction (the effect with increase is immediate though). If any replication consistency problems are encountered, it's recommended to set this back to ``1`` to see if that resolves the issue. The default value can be increased for better throughput. You may want to increase it many a time as suggested `in Codership documentation <http://galeracluster.com/documentation-webpages/nodestates.html#flow-control>`_, in ``JOINED`` state for instance to speed up the catchup process to ``SYNCED``. You can also estimate the optimal value for this from :variable:`wsrep_cert_deps_distance` as suggested `on this page <http://galeracluster.com/documentation-webpages/monitoringthecluster.html#checking-the-replication-health>`_. You can also refer to `this <http://galeracluster.com/documentation-webpages/configurationtips.html#setting-parallel-slave-threads>`_ for more configuration tips.
375
376 .. variable:: wsrep_sst_auth
377
378@@ -372,7 +402,7 @@
379 * xtrabackup-v2 - This is same as xtrabackup SST except that it uses newer protocol, hence is not compatible. This is the **recommended** option for PXC 5.5.34 and above. For more details, please check :ref:`xtrabackup_sst` and :ref:`errata`. This is also the default SST method. For SST with older nodes (< 5.5.34), use xtrabackup as the SST method.
380 * rsync - uses ``rsync`` to perform the SST, this method doesn't use the :variable:`wsrep_sst_auth`
381 * mysqldump - uses ``mysqldump`` to perform the SST, this method requires :variable:`wsrep_sst_auth` to be set up with <user>:<password>, where user has root privileges on the server.
382- * custom_script_name - Galera supports `Scriptable State Snapshot Transfer <http://www.codership.com/wiki/doku.php?id=scriptable_state_snapshot_transfer>`_. This enables users to create their own custom script for performing an SST.
383+ * custom_script_name - Galera supports `Scriptable State Snapshot Transfer <http://galeracluster.com/documentation-webpages/statetransfer.html#scriptable-state-snapshot-transfer>`_. This enables users to create their own custom script for performing an SST.
384 * skip - this option can be used to skip the SST, it can be used when initially starting the cluster and manually restore the same data to all nodes. It shouldn't be used as permanent setting because it could lead to data inconsistency across the nodes.
385
386 .. note::

Subscribers

People subscribed via source and target branches