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

[Hrvoje Matijakovic]

[Raghavendra D Prabhu (raghavendra-prabhu)]

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.

[Raghavendra D Prabhu (raghavendra-prabhu)]

Please also add https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1394836

[lp:~hrvojem/percona-xtradb-cluster/rn-5.6.21-25.8]

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

=== modified file 'doc-pxc/source/conf.py'
--- doc-pxc/source/conf.py	2014-09-04 14:22:31 +0000
+++ doc-pxc/source/conf.py	2014-11-25 13:29:06 +0000
@@ -53,9 +53,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = '5.6.20'
+version = '5.6.21'
 # The full version, including alpha/beta/rc tags.
-release = '5.6.20-25.7'
+release = '5.6.21-25.8'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
@@ -145,6 +145,7 @@
 extlinks = {'bug': ('https://bugs.launchpad.net/percona-xtradb-cluster/+bug/%s',
                       '#'), 'mysqlbug': ('http://bugs.mysql.com/bug.php?id=%s',
                       '#'), 'githubbug': ('https://github.com/codership/galera/issues/%s',
+                      '#'), 'wsrepbug': ('https://github.com/codership/mysql-wsrep/issues/%s',
                       '#')}
 
 # A list of ignored prefixes for module index sorting.
 
=== modified file 'doc-pxc/source/howtos/cenots_howto.rst'
--- doc-pxc/source/howtos/cenots_howto.rst	2014-01-29 15:10:12 +0000
+++ doc-pxc/source/howtos/cenots_howto.rst	2014-11-25 13:29:06 +0000
@@ -76,6 +76,10 @@
 After this, first node can be started with the following command: ::
 
   [root@percona1 ~]# /etc/init.d/mysql bootstrap-pxc
+
+In case you're running this tutorial on *CentOS* 7 server, systemd bootstrap service should be used instead: ::
+
+  [root@percona1 ~]#  systemctl start [e-mail]
  
 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.
 
 
=== modified file 'doc-pxc/source/installation.rst'
--- doc-pxc/source/installation.rst	2014-01-29 15:10:12 +0000
+++ doc-pxc/source/installation.rst	2014-11-25 13:29:06 +0000
@@ -9,7 +9,7 @@
 
 Ready-to-use binaries are available from the *Percona XtraDB Cluster* `download page <http://www.percona.com/downloads/Percona-XtraDB-Cluster-56/>`_, including:
 
- * ``RPM`` packages for *RHEL* 5 and *RHEL* 6
+ * ``RPM`` packages for *RHEL* 5, *RHEL* 6, and *RHEL* 7
 
  * *Debian* packages
 
 
=== modified file 'doc-pxc/source/manual/bootstrap.rst'
--- doc-pxc/source/manual/bootstrap.rst	2013-11-21 11:29:19 +0000
+++ doc-pxc/source/manual/bootstrap.rst	2014-11-25 13:29:06 +0000
@@ -32,6 +32,12 @@
  
   /etc/init.d/mysql bootstrap-pxc
 
+.. note:: 
+
+   On CentOS/RHEL 7 following bootstrap command should be used: :: 
+
+    systemctl start [e-mail]
+
 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. 
 
 Other Reading
 
=== added file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.21-25.8.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.21-25.8.rst	1970-01-01 00:00:00 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.21-25.8.rst	2014-11-25 13:29:06 +0000
@@ -0,0 +1,70 @@
+.. rn:: 5.6.21-25.8
+
+======================================
+ |Percona XtraDB Cluster| 5.6.21-25.8 
+======================================
+
+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>`.
+
+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.
+
+New Features
+============
+
+ 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`).
+
+ |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`).
+
+ |Percona XtraDB Cluster| is now shipped with Galera MTR test suite. 
+
+Bugs fixed 
+==========
+
+ |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`.
+
+ Fixed the ``UNIV_DEBUG`` build failures. Bug fixed :bug:`1384413`.
+
+ ``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`.
+ 
+ Normal shutdown under load would cause server to remain hanging because replayer failed to finish. Bug fixed :bug:`1358701`.
+
+ :variable:`wsrep_causal_reads` variable was not honored when declared as global. Bug fixed :bug:`1361859`.
+
+ Assertion failure ``lock != ctx->wait_lock`` has been fixed. Bug fixed :bug:`1364840`.
+
+ ``garbd`` would not work when cluster address was specified without the port. Bug fixed :bug:`1365193`.
+
+ Fixed wsrep options compiler warnings in *Fedora* 20. Bug fixed :bug:`1369916`.
+
+ 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`.
+
+ |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 ``[e-mail]`` (``/etc/sysconfig/bootstrap`` is supplied by default). Bug fixed :bug:`1381492`.
+
+ ``gvwstate.dat`` file was removed on joiner when :ref:`xtrabackup_sst` method was used. Bug fixed :bug:`1388059`.
+
+ |Percona XtraDB Cluster| now detects older joiners which don't have the backup lock support. Bug fixed :bug:`1390552`.
+
+ Longer ``wsrep-recover`` is now handled gracefully in Debian init scripts rather than returning immediately with a false positive fail.
+
+ ``wsrep-recover`` log is now also written to mysql error log now.
+
+ Issue with stale PID files and Debian init script have been fixed now. It now emits a warning for stale PID files. 
+
+ :file:`sst_in_progress` file is not removed anymore in case of failed SST.
+
+ 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`.
+ 
+ TOI now skips replication if all tables are temporary. Bugs fixed :wsrepbug:`11` and :wsrepbug:`13`.
+
+ 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`.
+
+ Bootstrapping a node tried to resolve gcomm address list specified in :variable:`wsrep-cluster-address`. Bug fixed :githubbug:`88`.
+
+ ``xtrabackup-v2`` SST did not clean the undo log directory. Bug fixed :bug:`1394836`.
+
+ 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`.
+
+Other bugs fixed :bug:`1378138`, :bug:`1377226`, :bug:`1376965`, :bug:`1356859`, :bug:`1026181`, :bug:`1367173`, :bug:`1390482`, :bug:`1391634`, and :bug:`1392369`.
+
+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-09-01 14:11:54 +0000
+++ doc-pxc/source/release-notes/release-notes_index.rst	2014-11-25 13:29:06 +0000
@@ -6,6 +6,7 @@
    :maxdepth: 1
    :glob:
 
+   Percona-XtraDB-Cluster-5.6.21-25.8
    Percona-XtraDB-Cluster-5.6.20-25.7
    Percona-XtraDB-Cluster-5.6.19-25.6
    Percona-XtraDB-Cluster-5.6.15-25.5
 
=== modified file 'doc-pxc/source/wsrep-provider-index.rst'
--- doc-pxc/source/wsrep-provider-index.rst	2014-07-18 11:33:37 +0000
+++ doc-pxc/source/wsrep-provider-index.rst	2014-11-25 13:29:06 +0000
@@ -50,6 +50,17 @@
    :dyn: No
    :default: no
 
+.. variable:: evs.auto_evict
+  
+   :version: Introduced in :rn:`5.6.21-25.8`
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: 0
+
+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``. 
+
 .. variable:: evs.causal_keepalive_period
 
    :cli: Yes
@@ -70,6 +81,38 @@
 
 This variable is used for EVS (Extended Virtual Synchrony) debugging it can be used only when :variable:`wsrep_debug` is set to ``ON``.
 
+.. variable:: evs.delay_margin
+
+   :version: Introduced in :rn:`5.6.21-25.8`
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: PT1S
+
+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.
+
+.. variable:: evs.delayed_keep_period
+
+   :version: Introduced in :rn:`5.6.21-25.8`
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: PT30S
+
+Time period that node is required to remain responsive until one entry is removed from delayed list.
+
+.. variable:: evs.evict
+
+   :version: Introduced in :rn:`5.6.21-25.8`
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+
+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.
+
 .. variable:: evs.inactive_check_period
 
    :cli: Yes
@@ -198,6 +241,8 @@
    :dyn: No
    :default: 0
 
+This variable defines the EVS protocol version. Auto eviction is enabled when this variable is set to ``1``. Default 0 for backwards compatibility.
+
 .. variable:: evs.view_forget_timeout
 
    :cli: Yes
 
=== modified file 'doc-pxc/source/wsrep-status-index.rst'
--- doc-pxc/source/wsrep-status-index.rst	2014-07-18 11:33:37 +0000
+++ doc-pxc/source/wsrep-status-index.rst	2014-11-25 13:29:06 +0000
@@ -26,12 +26,20 @@
 
 .. variable:: wsrep_repl_keys
 
+Total number of keys replicated.
+
 .. variable:: wsrep_repl_keys_bytes
 
+Total size (in bytes) of keys replicated.
+
 .. variable:: wsrep_repl_data_bytes
 
+Total size (in bytes) of data replicated.
+
 .. variable:: wsrep_repl_other_bytes
 
+Total size of other bits replicated.
+
 .. variable:: wsrep_received
   
 Total number of writesets received from other nodes. 
@@ -74,6 +82,8 @@
 
 .. variable:: wsrep_flow_control_paused_ns
 
+The total time spent in a paused state measured in nanoseconds.
+
 .. variable:: wsrep_flow_control_paused
   
 Time since the last status query that replication was paused due to flow control.
@@ -128,6 +138,8 @@
 
 .. variable:: wsrep_cert_index_size
   
+This variable shows the number of entries in the certification index.
+
 .. variable:: wsrep_causal_reads_
 
 Shows the number of writesets processed while the variable :variable:`wsrep_causal_reads` was set to ``ON``.
@@ -140,6 +152,18 @@
 
 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.
   
+.. variable:: wsrep_evs_delayed
+
+List of UUIDs of the evicted nodes.
+
+.. variable:: wsrep_evs_evict_list
+
+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.
+
+.. variable:: wsrep_evs_state
+
+Internal EVS protocol state.
+
 .. variable:: wsrep_cluster_conf_id
 
 Number of cluster membership changes happened.
@@ -160,6 +184,8 @@
   * ``Disconnected`` -
   
 .. variable:: wsrep_connected
+
+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. 
   
 .. variable:: wsrep_local_bf_aborts
   
 
=== modified file 'doc-pxc/source/wsrep-system-index.rst'
--- doc-pxc/source/wsrep-system-index.rst	2014-09-01 14:11:54 +0000
+++ doc-pxc/source/wsrep-system-index.rst	2014-11-25 13:29:06 +0000
@@ -53,7 +53,7 @@
    :cli: Yes
    :conf: Yes
    :scope: Global
-   :dyn: No
+   :dyn: Yes
 
 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: ::