Merge lp:~hrvojem/percona-xtradb-cluster/rn-5.6.20-25.7-5.6 into lp:percona-xtradb-cluster

[Hrvoje Matijakovic]

[Raghavendra D Prabhu (raghavendra-prabhu)]

In addition to below, (ignore if already added)

https://github.com/codership/galera/issues/95
https://github.com/codership/galera/issues/84
https://github.com/codership/galera/issues/75
https://github.com/codership/galera/issues/67

Documentation from those issues can be replicated to ours. They should be in galera tree (if not on their website).

[Raghavendra D Prabhu (raghavendra-prabhu)]

review: Needs Fixing

[Raghavendra D Prabhu (raghavendra-prabhu)]

Minor changes required.

One more thing to add: (under bugs)

Session-level binlog_format change to STATEMENT is allowed to support pt-table-checksum. A warning (to not use it otherwise) is also added to error log.

[lp:~hrvojem/percona-xtradb-cluster/rn-5.6.20-25.7-5.6]

865. By Hrvoje Matijakovic on 2014-09-01

Release notes for Percona-XtraDB-Cluster-5.6.20-25.7

[Raghavendra D Prabhu (raghavendra-prabhu)]

Approved.

review: Approve

=== modified file 'doc-pxc/source/manual/state_snapshot_transfer.rst'
--- doc-pxc/source/manual/state_snapshot_transfer.rst	2014-07-18 11:33:37 +0000
+++ doc-pxc/source/manual/state_snapshot_transfer.rst	2014-09-01 14:13:08 +0000
@@ -11,6 +11,11 @@
 
  If the variable :variable:`gcs.sync_donor` is set to ``Yes`` (default ``No``), whole cluster will get blocked if the donor is blocked by the State Snapshot Transfer and not just the donor node.
 
+Choosing the SST Donor
+======================
+
+If there are no nodes available that can safely perform an incremental state transfer, the cluster defaults to a state snapshot transfer. If there are nodes available that can safely perform an incremental state transfer, the cluster prefers a local node over remote nodes to serve as the donor. If there are no local nodes available that can safely perform an incremental state transfer, the cluster chooses a remote node to serve as the donor. Where there are several local or remote nodes available that can safely perform an incremental state transfer, the cluster chooses the node with the highest ``seqno`` to serve as the donor.
+
 Using *Percona Xtrabackup*
 ==========================
 

=== modified file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.19-25.6.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.19-25.6.rst	2014-07-18 11:33:37 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.19-25.6.rst	2014-09-01 14:13:08 +0000
@@ -1,4 +1,4 @@
-.. rn:: 5.6.17-25.6
+.. rn:: 5.6.19-25.6
 
 ======================================
  |Percona XtraDB Cluster| 5.6.19-25.6 

=== added file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.20-25.7.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.20-25.7.rst	1970-01-01 00:00:00 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.20-25.7.rst	2014-09-01 14:13:08 +0000
@@ -0,0 +1,48 @@
+.. rn:: 5.6.20-25.7
+
+======================================
+ |Percona XtraDB Cluster| 5.6.20-25.7 
+======================================
+
+Percona is glad to announce the release of |Percona XtraDB Cluster| 5.6 on September 1st 2014. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster-56/release-5.6.20-25.7/>`_ or from our :doc:`software repositories </installation>`.
+
+Based on `Percona Server 5.6.20-68.0 <http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.20-68.0.html>`_ including all the bug fixes in it, `Galera Replicator 3.7 <https://github.com/codership/galera/issues?milestone=1&page=1&state=closed>`_ and on `Codership wsrep API 25.7 <https://launchpad.net/wsrep-group/+milestone/5.6.20-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.20-25.7 milestone <https://launchpad.net/percona-xtradb-cluster/+milestone/5.6.20-25.7>`_ at Launchpad.
+
+New Features
+============
+ 
+ `systemd <http://freedesktop.org/wiki/Software/systemd/>`_ integration with *RHEL*/*CentOS* 7 is now available for |Percona XtraDB Cluster| (:bug:`1342223`).
+
+ New session variable :variable:`wsrep_sync_wait` has been implemented to control causality check. The old session variable :variable:`wsrep_causal_reads` is deprecated but is kept for backward compatibility (:bug:`1277053`).
+
+Bugs fixed 
+==========
+
+ Running ``START TRANSACTION WITH CONSISTENT SNAPSHOT``, ``mysqldump`` with :option:`--single-transaction` or ``mydumper`` with disabled binlog would lead to a server crash. Bug fixed :bug:`1353644`.
+
+ ``percona-xtradb-cluster-garbd-3.x`` package was installed incorrectly on *Debian*/*Ubuntu*. Bug fixed :bug:`1360633`.
+
+ Fixed ``netcat`` in SST script for Centos7 ``nmap-ncat``. Bug fixed :bug:`1359767`.
+
+ TO isolation was run even when wsrep plugin was not loaded. Bug fixed :bug:`1358681`.
+
+ The error from net read was not handled in native |MySQL| mode. This would cause duplicate key error if there was unfinished transaction at the time of shutdown, because it would be committed during the startup recovery. Bug fixed :bug:`1358264`.
+
+ The netcat in garbd init script has been replaced with nmap for compatibility in *CentOS* 7. Bug fixed :bug:`1349384`.
+
+ ``SHOW STATUS`` was generating debug output in the error log. Bug fixed :bug:`1347818`.
+
+ Incorrect source string length could lead to server crash. This fix allows maximum of 3500 bytes of key material to be populated, longer keys will be truncated. Bug fixed :bug:`1347768`.
+
+ A memory leak in ``wsrep_mysql_parse`` function has been fixed. Bug fixed :bug:`1345023`.
+
+ wsrep consistency check is now enabled for ``REPLACE ... SELECT`` as well. This was implemented because ``pt-table-checksum`` uses ``REPLACE .. SELECT`` during checksumming. Bug fixed :bug:`1343209`.
+ 
+ Client connections were closed unconditionally before generating SST request. Fixed by avoiding closing connections when wsrep is initialized before storage engines. Bug fixed :bug:`1258658`.
+ 
+ Session-level binlog_format change to ``STATEMENT`` is now allowed to support ``pt-table-checksum``. A warning (to not use it otherwise) is also added to error log.
+
+Other bug fixes: :bug:`1280270`.
+
+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!
+

=== modified file 'doc-pxc/source/release-notes/release-notes_index.rst'
--- doc-pxc/source/release-notes/release-notes_index.rst	2014-07-18 11:33:37 +0000
+++ doc-pxc/source/release-notes/release-notes_index.rst	2014-09-01 14:13:08 +0000
@@ -6,6 +6,7 @@
    :maxdepth: 1
    :glob:
 
+   Percona-XtraDB-Cluster-5.6.20-25.7
    Percona-XtraDB-Cluster-5.6.19-25.6
    Percona-XtraDB-Cluster-5.6.15-25.5
    Percona-XtraDB-Cluster-5.6.15-25.4

=== modified file 'doc-pxc/source/wsrep-files-index.rst'
--- doc-pxc/source/wsrep-files-index.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/wsrep-files-index.rst	2014-09-01 14:13:08 +0000
@@ -66,3 +66,25 @@
     seqno:   -1
     cert_index:
 
+* :file:`gvwstate.dat`
+  This file is used for Primary Component recovery feature. This file is created once primary component is formed or changed, so you can get the latest primary component this node was in. And this file is deleted when the node is shutdown gracefully.
+
+  First part contains the node UUID information. Second part contains the view information. View information is written between ``#vwbeg`` and ``#vwend``. View information consists of:
+
+ - view_id: [view_type] [view_uuid] [view_seq]. - ``view_type`` is always ``3`` which means primary view. ``view_uuid`` and ``view_seq`` identifies a unique view, which could be perceived as identifier of this primary component.
+
+ - bootstrap: [bootstarp_or_not]. - It could be ``0`` or ``1``, but it does not affect primary component recovery process now.
+
+ - member: [node's uuid] [node's segment]. - it represents all nodes in this primary component.
+
+   Example of this file looks like this: ::
+
+    my_uuid: c5d5d990-30ee-11e4-aab1-46d0ed84b408
+    #vwbeg
+    view_id: 3 bc85bd53-31ac-11e4-9895-1f2ce13f2542 2
+    bootstrap: 0
+    member: bc85bd53-31ac-11e4-9895-1f2ce13f2542 0
+    member: c5d5d990-30ee-11e4-aab1-46d0ed84b408 0
+    #vwend
+
+

=== modified file 'doc-pxc/source/wsrep-system-index.rst'
--- doc-pxc/source/wsrep-system-index.rst	2014-07-18 11:33:37 +0000
+++ doc-pxc/source/wsrep-system-index.rst	2014-09-01 14:13:08 +0000
@@ -29,6 +29,7 @@
 
 .. variable:: wsrep_causal_reads
 
+   :version 5.6.20-25.7: Variable deprecated by :variable:`wsrep_sync_wait`
    :cli: Yes
    :conf: Yes
    :scope: Global, Local
@@ -431,3 +432,20 @@
 
 This variable contains the ``UUID:seqno`` value. By setting all the nodes to have the same value for this option cluster can be set up without the state transfer.
 
+.. variable:: wsrep_sync_wait
+
+   :version 5.6.20-25.7: Variable introduced
+   :cli: Yes
+   :conf: Yes
+   :scope: Global, Session
+   :dyn: Yes
+
+This variable is used to control causality checks on some SQL statements, such as ``SELECT``, ``BEGIN``/``END``, ``SHOW STATUS``, but not on some autocommit SQL statements ``UPDATE`` and ``INSERT``. Causality check is determined by bitmask: 
+
+ * ``1`` Indicates check on ``READ`` statements, including ``SELECT``, ``SHOW``, ``BEGIN``/``START TRANSACTION``.
+
+ * ``2`` Indicates check on ``UPDATE`` and ``DELETE`` statements.
+
+ * ``4`` Indicates check on ``INSERT`` and ``REPLACE`` statements
+
+This variable deprecates the :variable:`wsrep_causal_reads` variable. Setting :variable:`wsrep_sync_wait` to ``1`` is the equivalent of setting :variable:`wsrep_causal_reads` to ``ON``.