Merge lp:~hrvojem/percona-xtradb-cluster/doc-58 into lp:percona-xtradb-cluster

[Hrvoje Matijakovic]

[Raghavendra D Prabhu (raghavendra-prabhu)]

Approved after changes and discussion.

review: Approve

=== modified file 'doc-pxc/source/conf.py'
--- doc-pxc/source/conf.py	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/conf.py	2013-11-21 11:30:55 +0000
@@ -53,9 +53,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = '5.5.31'
+version = '5.6.14'
 # The full version, including alpha/beta/rc tags.
-release = '5.5.31-23.7.5'
+release = '5.6.14-25.1'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
@@ -171,7 +171,7 @@
 html_title = 'Percona XtraDB Cluster Documentation'
 
 # A shorter title for the navigation bar.  Default is the same as html_title.
-html_short_title = 'XtraDB Cluster Docs'
+html_short_title = 'Percona XtraDB Cluster 5.6 Documentation'
 
 # The name of an image file (relative to this directory) to place at the top
 # of the sidebar.
@@ -244,7 +244,7 @@
 # Grouping the document tree into LaTeX files. List of tuples
 # (source start file, target name, title, author, documentclass [howto/manual]).
 latex_documents = [
-  ('index', 'PerconaXtraDBCluster.tex', u'Percona XtraDB Cluster Documentation',
+  ('index', 'PerconaXtraDBCluster-5.6.tex', u'Percona XtraDB Cluster Documentation',
    u'Percona Ireland Ltd. 2012-2013', 'manual'),
 ]
 
 
=== added file 'doc-pxc/source/errata.rst'
--- doc-pxc/source/errata.rst	1970-01-01 00:00:00 +0000
+++ doc-pxc/source/errata.rst	2013-11-21 11:30:55 +0000
@@ -0,0 +1,23 @@
+.. _errata:
+
+===============================
+ Percona XtraDB Cluster Errata 
+===============================
+
+Known Issues
+-------------
+
+Following are issues which may impact you while running PXC:
+ - wsrep_causal_reads being ON can introduce temporary stalls due to MDL lock conflicts.
+ - Create Table As Select (CTAS) can cause deadlocks and server hang when used with explicit TEMPORARY tables.
+ - bug :bug:`1226185`: percona-xtrabackup-20 may get installed as a dependency instead of latest percona-xtrabackup during a fresh install due to certain yum issues. This can be avoided by specifying ``percona-xtrabackup`` explicitly in the install command line.
+ - bug :bug:`1192834`: Joiner may crash after SST from donor with compaction enabled. Workaround is to disable the index compaction (compact under [xtrabackup]), if enabled. This crash requires specific configuration, hence you may not be affected. Also, this doesn't require any fix from PXC, but Xtrabackup with the fix included should do.
+ - bug :bug:`1098566`: :variable:`innodb_data_home_dir`/:variable:`innodb_log_group_home_dir` is not supported. Depends on bug :bug:`1164945` for the fix.
+
+Also make sure to check limitations page :ref:`here <limitations>`. You can also review this `milestone <https://launchpad.net/percona-xtradb-cluster/+milestone/future-5.5>`_ for features/bugfixes to be included in future releases (i.e. releases after the upcoming/recent release).
+
+Incompatibilities
+-------------------
+
+Following are incompatibilities between PXC 5.5.33 (and higher) and older versions:
+ - wsrep_sst_donor now supports comma separated list of nodes as a consequence of bug :bug:`1129512`. This only affects if you use this option as a list. This is not compatible with nodes running older PXC, hence **entire** cluster will be affected as far as SST is concerned, since donor nodes won't recognise the request from joiner nodes if former are not upgraded. Minimal workaround is to upgrade Galera package or to not use this new feature (wsrep_sst_donor with single node can still be used). However, upgrading the full PXC is strongly recommended, however, just upgrading PXC galera package will do for this.
 
=== modified file 'doc-pxc/source/howtos/cenots_howto.rst'
--- doc-pxc/source/howtos/cenots_howto.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/howtos/cenots_howto.rst	2013-11-21 11:30:55 +0000
@@ -37,7 +37,7 @@
 
 Following command will install |Percona XtraDB Cluster| packages: :: 
 
-  $ yum install Percona-XtraDB-Cluster-server Percona-XtraDB-Cluster-client
+  $ yum install Percona-XtraDB-Cluster-server-56 Percona-XtraDB-Cluster-client-56
 
 When these two commands have been executed successfully on all three nodes |Percona XtraDB Cluster| is installed.
 
 
=== modified file 'doc-pxc/source/index.rst'
--- doc-pxc/source/index.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/index.rst	2013-11-21 11:30:55 +0000
@@ -3,29 +3,33 @@
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.
 
-==================================================
-Welcome to Percona XtraDB Cluster's documentation!
-==================================================
-
-Percona XtraDB Cluster is High Availability and Scalability solution for MySQL Users.
-
-Percona XtraDB Cluster provides:
+==========================================
+ Percona XtraDB Cluster 5.6 Documentation
+==========================================
+
+.. warning::
+
+   Please note: |Percona XtraDB Cluster| 5.6 is BETA quality software. It should *NOT* be used in production environments.
+
+|Percona XtraDB Cluster| is High Availability and Scalability solution for MySQL Users.
+
+|Percona XtraDB Cluster| provides:
  
- * Synchronous replication. Transaction either commited on all nodes or none.
+ * Synchronous replication. Transaction either committed on all nodes or none.
 
  * Multi-master replication. You can write to any node.
 
- * Parallel applying events on slave. Real “parallel replication”.
+ * Parallel applying events on slave. Real "parallel replication".
 
  * Automatic node provisioning.
 
  * Data consistency. No more unsynchronized slaves.
 
-Percona XtraDB Cluster is fully compatible with MySQL or Percona Server in the following meaning:
-
- * Data compatibility. Percona XtraDB Cluster works with databases created in MySQL / Percona Server
-
- * Application compatibility. There is no or minimal application changes required to start work with Percona XtraDB Cluster
+|Percona XtraDB Cluster| is fully compatible with |MySQL| or |Percona Server| in the following meaning:
+
+ * Data compatibility. |Percona XtraDB Cluster| works with databases created in |MySQL| / |Percona Server|.
+
+ * Application compatibility. There is no or minimal application changes required to start work with |Percona XtraDB Cluster|.
 
 
 Introduction
@@ -37,6 +41,7 @@
 
    intro
    limitation
+   errata
 
 Installation
 ============
@@ -47,6 +52,7 @@
 
    installation
    installation/compiling_xtradb_cluster
+   upgrading_guide_55_56
 
 Features
 ========
 
=== modified file 'doc-pxc/source/installation.rst'
--- doc-pxc/source/installation.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/installation.rst	2013-11-21 11:30:55 +0000
@@ -33,7 +33,7 @@
 
 Once the repository is set up, use the following commands: ::
 
-  $ yum install Percona-XtraDB-Cluster-server Percona-XtraDB-Cluster-client
+  $ yum install Percona-XtraDB-Cluster-server-56 Percona-XtraDB-Cluster-client-56
 
 More detailed example of the |Percona XtraDB Cluster| installation and configuration can be seen in :ref:`centos_howto` tutorial.
 
@@ -42,7 +42,7 @@
 
 Once the repository is set up, use the following commands: ::
 
-  $ sudo apt-get install percona-xtradb-cluster-server-5.5 percona-xtradb-cluster-client-5.5
+  $ sudo apt-get install percona-xtradb-cluster-server-5.6 percona-xtradb-cluster-client-5.6
 
 More detailed example of the |Percona XtraDB Cluster| installation and configuration can be seen in :ref:`ubuntu_howto` tutorial.
 
 
=== modified file 'doc-pxc/source/installation/apt_repo.rst'
--- doc-pxc/source/installation/apt_repo.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/installation/apt_repo.rst	2013-11-21 11:30:55 +0000
@@ -39,6 +39,7 @@
  * 12.04LTS precise
  * 12.10 quantal
  * 13.04 raring
+ * 13.10 saucy
 
 
 Install XtraDB Cluster
@@ -46,8 +47,7 @@
 
 Following command will install Cluster packages: :: 
 
-  $ sudo apt-get install percona-xtradb-cluster-client-5.5 \
-  percona-xtradb-cluster-server-5.5 percona-xtrabackup
+  $ sudo apt-get install percona-xtradb-cluster-client-5.6 percona-xtradb-cluster-server-5.6
 
 Percona `apt` Experimental repository
 =====================================
 
=== modified file 'doc-pxc/source/installation/compiling_xtradb_cluster.rst'
--- doc-pxc/source/installation/compiling_xtradb_cluster.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/installation/compiling_xtradb_cluster.rst	2013-11-21 11:30:55 +0000
@@ -4,7 +4,7 @@
 
 The source code is available from the *Launchpad* project `here <https://launchpad.net/percona-xtradb-cluster>`_. The easiest way to get the code is with :command:`bzr branch` of the desired release, such as the following: ::
 
-  bzr branch lp:percona-xtradb-cluster
+  bzr branch lp:percona-xtradb-cluster/5.6
 
 You should then have a directory named after the release you branched, such as ``percona-xtradb-cluster``.
 
 
=== modified file 'doc-pxc/source/installation/yum_repo.rst'
--- doc-pxc/source/installation/yum_repo.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/installation/yum_repo.rst	2013-11-21 11:30:55 +0000
@@ -30,7 +30,11 @@
 
 Following command will install Cluster packages: ::
 
-  $ yum install Percona-XtraDB-Cluster-server Percona-XtraDB-Cluster-client xtrabackup
+  $ yum install Percona-XtraDB-Cluster-server-56 Percona-XtraDB-Cluster-client-56 percona-xtrabackup
+
+.. warning:: 
+
+   In order to sucessfully install |Percona XtraDB Cluster| ``socat`` package will need to be installed first.
 
 Percona `yum` Experimental repository
 =====================================
 
=== modified file 'doc-pxc/source/intro.rst'
--- doc-pxc/source/intro.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/intro.rst	2013-11-21 11:30:55 +0000
@@ -49,14 +49,14 @@
 Components
 ==========
 
-*Percona XtraDB Cluster* is based on `Percona Server with XtraDB <http://www.percona.com/software/percona-server/>`_
+|Percona XtraDB Cluster| is based on `Percona Server with XtraDB <http://www.percona.com/software/percona-server/>`_
 and includes `Write Set Replication patches <https://launchpad.net/codership-mysql>`_.
-It uses  the  `Galera library <https://launchpad.net/galera>`_, version 2.x, 
+It uses  the  `Galera library <https://launchpad.net/galera>`_, version 3.x, 
 a generic Synchronous Multi-Master replication plugin for transactional applications. 
 
 Galera library is developed by `Codership Oy <http://www.codership.com/>`_.
 
-Galera 2.x supports such new features as:
+Galera 3.x supports such new features as:
  * Incremental State Transfer (|IST|), especially useful for WAN deployments,
  * RSU, Rolling Schema Update. Schema change does not block operations against table.
 
 
=== modified file 'doc-pxc/source/limitation.rst'
--- doc-pxc/source/limitation.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/limitation.rst	2013-11-21 11:30:55 +0000
@@ -9,14 +9,16 @@
  - Currently replication works only with |InnoDB| storage engine. Any writes to tables of other types, including system (mysql.*) tables, are not replicated. However, DDL statements are replicated in statement level, and changes to mysql.* tables will get replicated that way. So, you can safely issue: CREATE USER..., but issuing: INSERT INTO mysql.user..., will not be replicated.
 
  - Unsupported queries:
-    * LOCK/UNLOCK TABLES cannot be supported in multi-master setups.
+
+    * ``LOCK/UNLOCK TABLES`` cannot be supported in multi-master setups.
     * lock functions (GET_LOCK(), RELEASE_LOCK()... )
 
  - Query log cannot be directed to table. If you enable query logging, you must forward the log to a file: log_output = FILE. Use general_log and general_log_file to choose query logging and the log file name.
 
- - Maximum allowed transaction size is defined by wsrep_max_ws_rows and wsrep_max_ws_size. LOAD DATA INFILE processing will commit every 10K rows. So large transactions due to LOAD DATA will be split to series of small transactions.
-
- - Due to cluster level optimistic concurrency control, transaction issuing COMMIT may still be aborted at that stage. There can be two transactions writing to same rows and committing in separate XtraDB Cluster nodes, and only one of the them can successfully commit. The failing one will be aborted. For cluster level aborts, XtraDB Cluster gives back deadlock error code: 
+ - Maximum allowed transaction size is defined by :variable:`wsrep_max_ws_rows` and :variable:`wsrep_max_ws_size` variables. ``LOAD DATA INFILE`` processing will commit every 10K rows. So large transactions due to ``LOAD DATA`` will be split to series of small transactions.
+
+ - Due to cluster level optimistic concurrency control, transaction issuing ``COMMIT`` may still be aborted at that stage. There can be two transactions writing to same rows and committing in separate |Percona XtraDB Cluster| nodes, and only one of the them can successfully commit. The failing one will be aborted. For cluster level aborts, |Percona XtraDB Cluster| gives back deadlock error code: ::
+
    (Error: 1213 SQLSTATE: 40001  (ER_LOCK_DEADLOCK)).
 
  - XA transactions can not be supported due to possible rollback on commit.
 
=== modified file 'doc-pxc/source/manual/bootstrap.rst'
--- doc-pxc/source/manual/bootstrap.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/manual/bootstrap.rst	2013-11-21 11:30:55 +0000
@@ -34,11 +34,6 @@
 
 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. 
 
-Version Specific Information
-============================
-
- * :rn:`5.5.31-23.7.5` - New bootstrap init script option ``bootstrap-pxc`` introduced.
-
 Other Reading
 =============
 
 
=== modified file 'doc-pxc/source/manual/state_snapshot_transfer.rst'
--- doc-pxc/source/manual/state_snapshot_transfer.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/manual/state_snapshot_transfer.rst	2013-11-21 11:30:55 +0000
@@ -20,32 +20,21 @@
 
   innobackupex --user=root --password=Passw0rd /tmp/
  
-Script used for this method can be found in :file:`/usr/bin/wsrep_sst_xtrabackup` and it's provided with the |PXC| binary packages.
-
-After :rn:`5.5.31-23.7.5` this method introduced the new :file:`my.cnf` option which can be used to set |XtraBackup| streaming option: :: 
-
-  [sst]
-  streamfmt=xbstream 
-
-Currently supported formats are tar (default, used in previous releases) and `xbstream <http://www.percona.com/doc/percona-xtrabackup/2.1/xbstream/xbstream.html>`_. Some of the benefits of choosing the xbstream over tar is that it supports more advanced features like `encrypted <http://www.percona.com/doc/percona-xtrabackup/2.1/innobackupex/encrypted_backups_innobackupex.html>`_, `compact <http://www.percona.com/doc/percona-xtrabackup/2.1/xbstream/xbstream.html>`_ and `compressed <http://www.percona.com/doc/percona-xtrabackup/2.1/innobackupex/streaming_backups_innobackupex.html#examples-using-xbstream>`_ backups.
-
-.. note::
-
-  Currently there is a limitations when using the ``xbstream`` option that the :term:`datadir` needs to be empty before starting the SST or otherwise the process will fail and the node will not be able to join the cluster.
+Script used for this method can be found in :file:`/usr/bin/wsrep_sst_xtrabackup` and it's provided with the |Percona XtraDB Cluster| binary packages. Detailed information on this method are provided in :ref:`xtrabackup_sst` documentation.
 
 Using ``mysqldump``
 ===================
 
 This method uses the standard :program:`mysqldump` to dump all the databases from the donor node and import them to the joining node. For this method to work :variable:`wsrep_sst_auth` needs to be set up with the root credentials. This method is the slowest one and it also performs the global lock while doing the |SST| which will block writes to the donor node.
 
-Script used for this method can be found in :file:`/usr/bin/wsrep_sst_mysqldump` and it's provided with the |PXC| binary packages.
+Script used for this method can be found in :file:`/usr/bin/wsrep_sst_mysqldump` and it's provided with the |Percona XtraDB Cluster| binary packages.
 
 Using ``rsync``
 ===============
 
 This method uses :program:`rsync` to copy files from donor to the joining node. In some cases this can be faster than using the |XtraBackup| but requires the global data lock which will block writes to the donor node. This method doesn't require username/password credentials to be set up in the variable :variable:`wsrep_sst_auth`.
 
-Script used for this method can be found in :file:`/usr/bin/wsrep_sst_rsync` and it's provided with the |PXC| binary packages.
+Script used for this method can be found in :file:`/usr/bin/wsrep_sst_rsync` and it's provided with the |Percona XtraDB Cluster| binary packages.
 
 Other Reading
 =============
 
=== modified file 'doc-pxc/source/manual/xtrabackup_sst.rst'
--- doc-pxc/source/manual/xtrabackup_sst.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/manual/xtrabackup_sst.rst	2013-11-21 11:30:55 +0000
@@ -4,6 +4,17 @@
  Xtrabackup SST Configuration
 ===============================
 
+XtraBackup SST works in two stages:
+
+ * Stage I on joiner checks if it is |SST| or |IST| based on presence of :file:`xtrabackup_ist` file. 
+ * In Stage II it starts the data transfer, if it's |SST|, it empties the data directory sans few files (galera.cache, sst_in_progress, grastate.dat) and then proceed with the SST or if it's IST, proceeds as before.
+
+.. note::
+
+   To maintain compatibility with |Percona XtraDB Cluster| older than 5.5.33-23.7.6, use xtrabackup as SST method, else xtrabackup-v2 is recommended
+
+Latest |Percona Xtrabackup| 2.1.x is strongly recommended for Xtrabackup SST. Refer to `Incompatibilities <http://www.percona.com/doc/percona-xtradb-cluster/errata.html#incompatibilities>`_ for possible caveats.
+
 Following SST specific options are allowed in my.cnf under [sst]                                     
 -----------------------------------------------------------------
       
@@ -18,15 +29,13 @@
           
         * In following options, path always means full path.
 
-        * Following options are only applicable for **PXC 5.5.32** and above. For 5.5.31 PXC refer to documentation in wsrep_sst_xtrabackup.
-
 .. option:: streamfmt
 
      :Values: xbstream, tar  
-     :Default: tar             
+     :Default: xbstream
      :Match: Yes
 
-Refer to :ref:`Xbstream v/s Tar<tar_ag_xbstream>` for details and caveats of using tar v/s xbstream for SST.
+Xbstream is highly recommended. Refer to :ref:`Xbstream v/s Tar <tar_ag_xbstream>` for details and caveats of using tar v/s xbstream for SST.
              
 .. option:: transferfmt
 
@@ -39,30 +48,33 @@
 .. option:: tca 
 
      :Description: CA file for openssl based encryption with socat.                                                   
-     :Type: Full path to CA file.
+     :Type: Full path to CRT file (.crt).
                           
 .. option:: tcert
     
     :Description: PEM for openssl based encryption with socat.                                                     
-    :Type:  Full path to PEM.
+    :Type:  Full path to PEM (.pem).
 
 .. note::
-    For tca and tcert, refer to http://www.dest-unreach.org/socat/doc/socat-openssltunnel.html for an example.      
+    For tca and tcert, refer to http://www.dest-unreach.org/socat/doc/socat-openssltunnel.html for an example. The ``tca`` is essentially the self-signed certificate in that example, and ``tcert`` is the PEM file generated after concatenation of the key and the certificate generated earlier. The names of options were chosen so as to be compatible with socat's parameter' names as well as with MySQL's SSL authentication. For testing you can also download certificates from `launchpad <https://bazaar.launchpad.net/~percona-core/percona-xtradb-cluster/5.5/files/head:/tests/certs/>`_. **Note** that irrespective of what is shown in the example, you can use same crt and pem files on all nodes and it will work, since there is no server-client paradigm here but a cluster with homogeneous nodes.
                                                                                                              
 .. option:: encrypt
 
-    :Values: 0,1,2  
+    :Values: 0,1,2,3
     :Default: 0
     :Match: Yes
-    :Recommended: 2
 
 Decides whether encryption is to be done or not, if this is zero, no    
-encryption is done.                                                    
+encryption is done. ``encrypt=2`` is recommended if your nodes are      
+over WAN and security constraints are higher, while ``encrypt=1``       
+(Xtrabackup-based symmetric encryption) is easier to setup.             
 
   * Xtrabackup based encryption  with ``encrypt=1``.
 
   * OpenSSL based encryption with ``encrypt=2``. Socat must be built with openSSL for encryption: ``socat -V | grep OPENSSL``.
 
+  * 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>`.
+
 Refer to this :ref:`document <xtrabackup_sst_encryption>` when enabling with ``encrypt=1``.
 
 .. option:: encrypt-algo
@@ -78,13 +90,12 @@
 
 .. option:: progress
 
-    :Values: 1,path/to/file,path/to/fifo
+    :Values: 1,path/to/file
 
 If equal to:
 
     * 1 it writes to mysql stderr 
-    * path/to/file writes to that file. 
-    * path/to/fifo, it will be created and cleaned up at exit.This is the preferred way. You need to cat the fifo file to monitor the progress, not tail it.
+    * path/to/file writes to that file. If this is a fifo, it needs to exist and be open on reader end before itself, otherwise wsrep_sst_xtrabackup will block indefinitely.
 
 .. note::
     Value of 0 is not valid.
@@ -96,7 +107,9 @@
     
 Used only on joiner. 1 implies rebuild indexes. Note that this is       
 independent of compaction, though compaction enables it. Rebuild of     
-indexes may be used as an optimization.                                 
+indexes may be used as an optimization. Note that :bug:`1192834`        
+affects this, hence use of ``compact`` and ``rebuild`` are recommended  
+after that is fixed in Percona Xtrabackup and released.                 
                              
 .. option:: time
 
@@ -119,36 +132,63 @@
 To be set on joiner only, supersedes IST if set. Currently requires
 manual setup. Hence, not supported currently.
 
+.. option:: use_extra
+
+    :Values: 0,1
+    :Default: 0
+
+
+If set to 1, SST will use the thread pool's `extra_port <http://www.percona.com/doc/percona-server/5.6/performance/threadpool.html#extra_port>`_. Make sure that thread pool is enabled and extra_port option is set in my.cnf before you turn on this option.
+
+.. option:: cpat
+
+During the SST, the :term:`datadir` is cleaned up so that state of other node can be restored cleanly. This option provides the ability to define the files that need to be deleted before the SST. It can be set like: :: 
+
+  [sst]
+  cpat='.*galera\.cache$\|.*sst_in_progress$\|.*grastate\.dat$\|.*\.err$\|.*\.log$\|.*RPM_UPGRADE_MARKER$\|.*RPM_UPGRADE_HISTORY$\|.*\.xyz$'
+
+**NOTE:** This option can only be used when :variable:`wsrep_sst_method` is set to xtrabackup-v2.
+
 .. _tar_ag_xbstream:
 
 Tar against xbstream
 ---------------------
 
   * Features - encryption, compression, parallel streaming, streaming incremental backups, compaction - won't work with tar. Refer to `xbstream docs <http://www.percona.com/doc/percona-xtrabackup/2.1/xbstream/xbstream.html>`_ for more. 
-  * Bug :bug:`1193240` requires you to manually cleanup the directory (empty data directory) prior to SST. After that is fixed (and xtrabackup is released), SST will work without any modifications to wsrep_sst_xtrabackup.
 
 Xtrabackup SST Dependencies
 ----------------------------
 
 Following are optional dependencies of PXC introduced by wsrep_sst_xtrabackup: (obvious and direct dependencies are not provided here)
 
-    * qpress for decompression. It is a dependency of Xtrabackup 2.1.4 and is available in our repos.
+    * qpress for decompression. It is an optional dependency of |Percona XtraBackup| 2.1.4 and it is available in our software repositories.
     * my_print_defaults to extract values from my.cnf. Provided by the server package.
-    * openbsd-netcat or socat for transfer. socat is a direct dependency of PXC and is the default.
+    * openbsd-netcat or socat for transfer. socat is a direct dependency of |Percona XtraDB Cluster| and it is the default.
     * xbstream/tar for streaming. tar is default.
     * pv. Required for :option:`progress` and :option:`rlimit`. Provided by pv.
     * mkfifo. Required for :option:`progress`. Provided by coreutils.
     * mktemp. Required for :option:`incremental`. Provided by coreutils.
 
-.. _tip::
-    For qpress download `from <http://www.quicklz.com/qpress-11-linux-x64.tar>`_ till it is available. You can also build it from `source <http://www.quicklz.com/qpress-11-source.zip>`_.
+.. _galera_sst_encryption:
+
+Galera compatible encryption
+----------------------------
+
+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: ::
+
+   [sst] 
+   encrypt=3
+   tkey=/etc/mysql/key.pem
+   tcert=/etc/mysql/cert.pem
+
+**NOTE:** This option can only be used when :variable:`wsrep_sst_method` is set to xtrabackup-v2.
 
 .. _xtrabackup_sst_encryption:
 
 Xtrabackup-based encryption
 ----------------------------
 
-This is enabled when :option:`encrypt` is set to 1 under [sst]. However, due to lp:1190335, it will also be enabled when you specify any of the following options under [xtrabackup] in my.cnf:
+This is enabled when :option:`encrypt` is set to 1 under [sst]. However, due to bug :bug:`1190335`, it will also be enabled when you specify any of the following options under [xtrabackup] in my.cnf:
 
 .. _xtrabackup_encrypt_options:
 
@@ -158,11 +198,11 @@
 
 There is no way to disallow encryption from innobackupex if the above are in my.cnf under [xtrabackup]. For that reason, do the following:
 
-    #. If you want to use xtrabackup based encryption for SST but not otherwise, use ``encrypt=1`` under [sst] and provide xtrabackup_encrypt_options_ under [sst]. Details of those options can be found `here <http://www.percona.com/doc/percona-xtrabackup/2.1/innobackupex/encrypted_backups_innobackupex.html>`_.
-
-    #. If you want to use xtrabackup based encryption always, use ``encrypt=1`` under [sst] and have those xtrabackup_encrypt_options_ either under [sst] or [xtrabackup].
-
-    #. If you don't want xtrabackup based encryption for SST but want it otherwise, use ``encrypt=0`` or ``encrypt=2`` and do **NOT** provide xtrabackup_encrypt_options_ under [xtrabackup]. You can still have them under [sst] though. You will need to provide those options on innobackupex commandline then.
+    #. If you want to use xtrabackup based encryption for SST but not otherwise, use ``encrypt=1`` under [sst] and provide xtrabackup_encrypt_options under [sst]. Details of those options can be found `here <http://www.percona.com/doc/percona-xtrabackup/2.1/innobackupex/encrypted_backups_innobackupex.html>`_.
+
+    #. If you want to use xtrabackup based encryption always, use ``encrypt=1`` under [sst] and have those xtrabackup_encrypt_options either under [sst] or [xtrabackup].
+
+    #. If you don't want xtrabackup based encryption for SST but want it otherwise, use ``encrypt=0`` or ``encrypt=2`` and do **NOT** provide xtrabackup_encrypt_options under [xtrabackup]. You can still have them under [sst] though. You will need to provide those options on innobackupex commandline then.
 
     #. If you don't want to use xtrabackup based encryption at all (or only the openssl-based for SST with ``encrypt=2``), then you don't need worry about these options! (just don't provide them in my.cnf)
 
@@ -172,4 +212,4 @@
     The :option:`encrypt` under [sst] is different from under [xtrabackup]. The former is for disabling/changing encryption mode, latter is to provide encryption algorithm. To disambiguate, if you need to provide latter under [sst] (which you need to, for points #1 and #2 above) then it should be specified as :option:`encrypt-algo`.
 
 .. warning:: 
-    An implication of the above is that if you specify xtrabackup_encrypt_options_ but ``encrypt=0`` under [sst], it will **STILL** be encrypted and SST will fail. Look at point#3 above for resolution.
+    An implication of the above is that if you specify xtrabackup_encrypt_options but ``encrypt=0`` under [sst], it will **STILL** be encrypted and SST will fail. Look at point#3 above for resolution.
 
=== removed file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.23.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.23.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.23.rst	1970-01-01 00:00:00 +0000
@@ -1,19 +0,0 @@
-.. rn:: 5.5.23
-
-=====================================
- |Percona XtraDB Cluster| 5.5.23-23.5
-=====================================
-
-Percona is glad to announce the release of |Percona XtraDB Cluster| on May 14, 2012. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster/5.5.23-23.5/>`_ or from our `software repositories <http://www.percona.com/doc/percona-xtradb-cluster/installation.html#using-percona-software-repositories>`_.
-
-This is an General Availability release. We did our best to eliminate bugs and problems during alpha and beta testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_.
-
-List of changes:
-  * Fixes merged from upstream (`Codership-mysql <http://www.codership.com/content/wsrep-patch-235-mysql-5523-released>`_).
-  * Support for MyISAM, now changes to MyISAM tables are replicated to other nodes.
-  * Improvements to XtraBackup SST methods, better error handling.
-  * New SST wsrep_sst_method=skip, useful when you start all nodes from the same sources (i.e. backup).
-  * Ability to pass list of IP addresses for a new node, it will connect to the first available.
-
-Based on `Percona Server 5.5.23-25.3 <http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.23-25.3.html>`_ including all the bug fixes in it, and the latest `Galera 2.x replicator <https://code.launchpad.net/~codership/galera/2.x>`_,  |Percona XtraDB Cluster| 5.5.23-25.3 is now the current stable release. All of |Percona|'s software is open-source and free. 
-
 
=== removed file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.24.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.24.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.24.rst	1970-01-01 00:00:00 +0000
@@ -1,16 +0,0 @@
-.. rn:: 5.5.24
-
-=====================================
- |Percona XtraDB Cluster| 5.5.24-23.6
-=====================================
-
-Percona is glad to announce the release of |Percona XtraDB Cluster| on June 7, 2012. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster/5.5.24-23.6/>`_ or from our `software repositories <http://www.percona.com/doc/percona-xtradb-cluster/installation.html#using-percona-software-repositories>`_.
-
-This is an General Availability release. We did our best to eliminate bugs and problems during alpha and beta testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_.
-
-Bugs fixed: 
-
-  * Table with no PK but still having UK, can cause crash in slave using PA. Bug fixed :bug:`1003929`.
-
-Based on `Percona Server 5.5.24-26.0 <http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.24-26.0.html>`_ including all the bug fixes in it, and the latest `Galera 2.x replicator <https://code.launchpad.net/~codership/galera/2.x>`_,  |Percona XtraDB Cluster| 5.5.24-23.6 is now the current stable release. All of |Percona|'s software is open-source and free. 
-
 
=== removed file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.27.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.27.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.27.rst	1970-01-01 00:00:00 +0000
@@ -1,38 +0,0 @@
-.. rn:: 5.5.27
-
-=====================================
- |Percona XtraDB Cluster| 5.5.27-23.6
-=====================================
-
-Percona is glad to announce the release of |Percona XtraDB Cluster| on September 7th, 2012. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster/5.5.27-23.6/>`_ or from our `software repositories <http://www.percona.com/doc/percona-xtradb-cluster/installation.html#using-percona-software-repositories>`_.
-
-This is an General Availability release. We did our best to eliminate bugs and problems during the testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_.
-
-Features
-========
-
-  * |Percona XtraDB Cluster| supports tunable buffer size for fast index creation in |InnoDB|. This value was calculated based on the merge block size (which was hardcoded to 1 MB) and the minimum index record size. By adding the session variable `innodb_merge_sort_block_size <http://www.percona.com/doc/percona-server/5.5/management/innodb_fast_index_creation.html#innodb_merge_sort_block_size>`_ block size that is used in the merge sort can now be adjusted for better performance.
-
-  * |Percona XtraDB Cluster| has implemented ability to have a MySQL `Utility user <http://www.percona.com/doc/percona-server/5.5/management/utility_user.html#psaas-utility-user>`_ who has system access to do administrative tasks but limited access to user schema. This feature is especially useful to those operating MySQL As A Service.
-
-  * New  `Expanded Program Option Modifiers <http://www.percona.com/doc/percona-server/5.5/management/expanded_program_option_modifiers.html#expanded-option-modifiers>`_ have been added to allow access control to system variables.
-
-  * New table `INNODB_UNDO_LOGS <http://www.percona.com/doc/percona-server/5.5/diagnostics/misc_info_schema_tables.html#INNODB_UNDO_LOGS>`_ has been added to allow access to undo segment information. Each row represents an individual undo segment and contains information about which rollback segment the undo segment is currently owned by, which transaction is currently using the undo segment, and other size and type information for the undo segment. This information is 'live' and calculated for each query of the table.
-
-  * |Percona XtraDB Cluster| now has improved ``clustercheck.sh`` script which makes a proxy (ie HAProxy) capable of monitoring Percona XtraDB Cluster nodes properly.
-
-Bugs fixed 
-==========
-
-  * Increasing the number of slave threads doesn't require provider reloading anymore. Bug fixed :bug:`852094`. 
-
-  * No other SQL statement except INSERT...SELECT would replicate if /*!99997*/ comment was present. Bug fixed :bug:`1023911`.
- 
-  * Fixed the bug that caused DDL command hanging when RSU was enabled and server was under high rate SQL write load. Bug fixed :bug:`1026181`.
-
-  * Cascading foreign key constraint could cause a slave crash. Bug fixed :bug:`1013978`.
-
-  * Fixed bug when donor accepts query, which then blocks. Bug fixed :bug:`1002714`.
-
-Based on `Percona Server 5.5.27-28.1 <http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.27-28.1.html>`_ including all the bug fixes in it, and the latest `Galera 2.x replicator <https://code.launchpad.net/~codership/galera/2.x>`_,  |Percona XtraDB Cluster| 5.5.27-23.6 is now the current stable release. All of |Percona|'s software is open-source and free. 
-
 
=== removed file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.28.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.28.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.28.rst	1970-01-01 00:00:00 +0000
@@ -1,56 +0,0 @@
-.. rn:: 5.5.28-23.7
-
-======================================
- |Percona XtraDB Cluster| 5.5.28-23.7
-======================================
-
-Percona is glad to announce the release of |Percona XtraDB Cluster| on November 15th, 2012. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster/5.5.28-23.7/>`_ or from our `software repositories <http://www.percona.com/doc/percona-xtradb-cluster/installation.html#using-percona-software-repositories>`_.
-
-This is an General Availability release. We did our best to eliminate bugs and problems during the testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_.
-
-Features
-========
-
-  * |Percona XtraDB Cluster| has ported Twitter's |MySQL| ``NUMA`` patch. This patch `implements improved NUMA support <http://www.percona.com/doc/percona-server/5.5/performance/innodb_numa_support.html#innodb-numa-support>`_ as it prevents imbalanced memory allocation across NUMA nodes. 
-
-  * Number of binlog files can be restricted when using |Percona XtraDB Cluster| with the new `max_binlog_files <http://www.percona.com/doc/percona-server/5.5/flexibility/max_binlog_files.html#max_binlog_files>`_ option.
-
-  * New status variable :variable:`wsrep_incoming_addresses` has been introduced. It contains a comma-separated list of incoming (client) addresses in the cluster component.
-
-  * Multiple addresses can now be specified in the ``gcomm:// URL`` when defining the address to connect to cluster. Option :variable:`wsrep_urls` is now deprecated, :variable:`wsrep_cluster_address` should be used to specify multiple addresses instead.
-
-  * GTID can now be recovered by starting mysqld with ``--wsrep-recover`` option. This will parse GTID from log, and if the GTID is found, assign it as initial position for actual server start.
-
-  * ``SET PASSWORD`` command replication has been implemented. The SET statement can contain other variables and several password changes, and each password change will be replicated separately as one TOI (total order isolation) call. The user does not have to be explicitly defined, current user will be detected and correct ``SET PASSWORD`` statement will be generated for TOI replication in every use case.
-
-  * SQL statements aborted due to multi-master conflict can be automatically retried. This can be controlled with :variable:`wsrep_retry_autocommit` variable. The retrying will happen only if there is real abort for the SQL statement. If statement itself enters into commit phase and detects certification failure, there will be no retry.
- 
-  * This version of |Percona XtraDB Cluster| implements significant speedups and memory footprint reduction on ranged queries.
-
-Bugs fixed 
-==========
-
-  * Some wsrep variables, like :variable:`wsrep_provider`, :variable:`wsrep_provider_options` and :variable:`wsrep_cluster_address`, could be "doubly" allocated which could cause memory leak. Bug fixed :bug:`1072839`.
-
-  * In case variables :variable:`wsrep_node_address` and :variable:`wsrep_node_incoming_address` were not set explicitly, port number would be set to ``0``. Bug fixed :bug:`1071882`.
-
-  * Server would hang before storage engine initialization with ``rsync`` SST and with option :variable:`wsrep_start_position` enabled. Bug fixed :bug:`1075495`.
-
-  * SST script interface has been upgraded to use named instead of positional parameters. Bug fixed :bug:`1045026`.
-
-  * When server was started with no wsrep_provider and regular |MySQL| replication slave was configured, could cause intermittent failure to start MySQL slave during startup. Bug fixed :bug:`1075617`.
-
-  * If DDL is processing with RSU method and there is MDL conflict with local transaction, this conflict would remain unresolved. Bug fixed :bug:`1039514`.
-
-  * Static SST method list has been removed. Bug fixed :bug:`1045040`.
-
-  * DDL in multi-statement would cause a server crash. Bug fixed :bug:`1049024`.
-
-  * Mysqld_safe doesn't restart the node automatically anymore. Bug fixed :bug:`1077632`.
- 
-  * Server would fail to start if the variable :variable:`wsrep_provider` was unset. Bug fixed :bug:`1077652`.
-
-Other bug fixes: bug :bug:`1049103`, bug :bug:`1045811`, bug :bug:`1057910`, bug :bug:`1052668`, bug :bug:`1073220`, bug :bug:`1076382`.
-
-Based on `Percona Server 5.5.28-29.1 <http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.28-29.1.html>`_ including all the bug fixes in it, |Percona XtraDB Cluster| 5.5.28-23.7 is now the current stable release. All of |Percona|'s software is open-source and free. 
-
 
=== removed file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.29-23.7.2.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.29-23.7.2.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.29-23.7.2.rst	1970-01-01 00:00:00 +0000
@@ -1,20 +0,0 @@
-.. rn:: 5.5.29-23.7.2
-
-========================================
- |Percona XtraDB Cluster| 5.5.29-23.7.2
-========================================
-
-Percona is glad to announce the release of |Percona XtraDB Cluster| on February 12th, 2013. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster/5.5.29-23.7.2/>`_ or from our `software repositories <http://www.percona.com/doc/percona-xtradb-cluster/installation.html#using-percona-software-repositories>`_.
-
-This is an General Availability release. We did our best to eliminate bugs and problems during the testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_.
-
-
-Bugs fixed 
-==========
- 
- ``DML`` operations on temporary tables would try to append the key for provider library, which could cause a memory leak. Bug fixed for |MyISAM| temporary tables, |InnoDB| temporary tables still have this issue, probably caused by upstream bug :mysqlbug:`67259`. Bug fixed :bug:`1112514` (*Seppo Jaakola*).
-
- Bug fix for bug :bug:`1078346` introduced a regression. Foreign key checks were skipped in the parent table, which would cause the foreign key constraint errors. Bug fixed :bug:`1117175` (*Seppo Jaakola*).
-
-Based on `Percona Server 5.5.29-29.4 <http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.29-29.4.html>`_ including all the bug fixes in it, |Percona XtraDB Cluster| 5.5.29-23.7.2 is now the current stable release. All of |Percona|'s software is open-source and free. 
-
 
=== removed file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.29.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.29.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.29.rst	1970-01-01 00:00:00 +0000
@@ -1,44 +0,0 @@
-.. rn:: 5.5.29-23.7.1
-
-========================================
- |Percona XtraDB Cluster| 5.5.29-23.7.1
-========================================
-
-Percona is glad to announce the release of |Percona XtraDB Cluster| on January 30th, 2013. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster/5.5.29-23.7.1/>`_ or from our `software repositories <http://www.percona.com/doc/percona-xtradb-cluster/installation.html#using-percona-software-repositories>`_.
-
-This is an General Availability release. We did our best to eliminate bugs and problems during the testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_.
-
-
-Bugs fixed 
-==========
-
-  In some cases when node is recovered variable :variable:`threads_running` would become huge. Bug fixed :bug:`1040108` (*Teemu Ollakka*).
-
-  Variable :variable:`wsrep_defaults_file` would be set up to the value in the last configuration file read. Bug fixed by keeping the value found in the top configuration file. Bug fixed :bug:`1079892` (*Alex Yurchenko*).
-
-  Variable :variable:`wsrep_node_name` was initialized before the ``glob_hostname``, which lead to empty value for :variable:`wsrep_node_name` if it wasn't set explicitly. Bug fixed :bug:`1081389` (*Alex Yurchenko*). 
-
-  Running ``FLUSH TABLES WITH READ LOCK`` when slave applier needed to abort transaction that is on the way caused the deadlock situation. Resolved by grabbing Global Read Lock before pausing wsrep provider. Bug fixed :bug:`1083162` (*Teemu Ollakka*).
-
-  |Percona XtraDB Cluster| would crash when processing a delete for a table with foreign key constraint. Bug fixed :bug:`1078346` (*Seppo Jaakola*).
-
-  When variable :variable:`innodb_support_xa` was set to ``0``, wsrep position wasn't stored into the InnoDB tablespace. Bug fixed :bug:`1084199` (*Teemu Ollakka*).
-
-  Using |XtraBackup| for State Snapshot Transfer would fail due to ``mktemp`` error. Bug fixed :bug:`1080829` (*Alex Yurchenko*).
-
-  |XtraBackup| donor would run |XtraBackup| indefinitely if the xtrabackup ``--tmpdir`` was on ``tmpfs``. Bug fixed :bug:`1086978` (*Alex Yurchenko*).
-
-  In some cases non-uniform foreign key reference could cause a slave crash. Fixed by using primary key of the child table when appending exclusive key for cascading delete operation. Bug fixed :bug:`1089490` (*Seppo Jaakola*).
-
-  |Percona XtraDB Cluster| would crash when :variable:`binlog_format` was set to ``STATEMENT``. This was fixed by introducing the warning message. Bug fixed :bug:`1088400` (*Seppo Jaakola*).
-
-  An explicitly set :variable:`wsrep_node_incoming_address` may make "``SHOW STATUS LIKE 'wsrep_incoming_addresses';``" return the address without the port number. Bug fixed :bug:`1082406` (*Alex Yurchenko*).
-
-  |Percona XtraDB Cluster| would crash if the node's own address would be specified in the :variable:`wsrep_cluster_address` variable. Bug fixed :bug:`1099413`. (*Alexey Yurchenko*)
-
-  When installing from yum repository, ``Percona-XtraDB-Cluster-server`` and ``Percona-XtraDB-Cluster-client`` would conflict with ``mysql`` and ``mysql-server`` packages. Bug fixed :bug:`1087506` (*Ignacio Nin*).
-
-Other bug fixes: bug fixed :bug:`1037165`, bug fixed :bug:`812059`.
-
-Based on `Percona Server 5.5.29-29.4 <http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.29-29.4.html>`_ including all the bug fixes in it, |Percona XtraDB Cluster| 5.5.29-23.7.1 is now the current stable release. All of |Percona|'s software is open-source and free. 
-
 
=== removed file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.30-23.7.4.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.30-23.7.4.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.30-23.7.4.rst	1970-01-01 00:00:00 +0000
@@ -1,84 +0,0 @@
-.. rn:: 5.5.30-23.7.4
-
-========================================
- |Percona XtraDB Cluster| 5.5.30-23.7.4
-========================================
-
-Percona is glad to announce the release of |Percona XtraDB Cluster| on April 17th, 2013. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster/5.5.30-23.7.4/>`_ or from our :doc:`software repositories </installation>`.
-
-This is an General Availability release. We did our best to eliminate bugs and problems during the testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_.
-
-New Features
-============
-
- |Percona XtraDB Cluster| has implemented initial implementation of weighted quorum. Weight for node can be assigned via :variable:`pc.weight` option in the :variable:`wsrep_provider_options` variable. Accepted values are in the range [0, 255] (inclusive). Quorum is computed using weighted sum over group members.
-
- |Percona XtraDB Cluster| binary will now be shipped with the ``libjemalloc`` library. For ``rpm/deb`` packages, this library will be available for download from our repositories. Benchmark showing the impact of memory allocators on |MySQL| performance can be found in this `blogpost <http://www.mysqlperformanceblog.com/2012/07/05/impact-of-memory-allocators-on-mysql-performance/>`_.
-
- This release of |Percona XtraDB Cluster| has fixed number of foreign key and packaging bugs.
-
-Bugs fixed 
-==========
- 
- Fixed yum dependencies that were causing conflicts in ``CentOS`` 6.3 during installation. Bug fixed :bug:`1031427` (*Ignacio Nin*).
-
- In case the |Percona XtraDB Cluster| was built from the source rpm, wsrep revision information would be missing. Bug fixed :bug:`1128906` (*Alexey Bychko*).
-
- The method of generating md5 digest over tuples in a table with no primary key was not deterministic and this could cause a node failure. Bug fixed :bug:`1019473` (*Seppo Jaakola*).
-
- |Percona XtraDB Cluster| was built with YaSSL which could cause some of the programs that use it to crash. Fixed by building packages with OpenSSL support rather than the bundled YaSSL library. Bug fixed :bug:`1104977` (*Raghavendra D Prabhu*).
-
- Clustercheck script would hang in case the |MySQL| server on a node is hung. As a consequence clustercheck script would never fail-over that server. Bug fixed :bug:`1035927` (*Raghavendra D Prabhu*).
-
- High values in variables :variable:`evs.send_window` and :variable:`evs.user_send_window` could trigger cluster crash under high load. Bug fixed :bug:`1080539` (*Teemu Ollakka*).
-
- Standard |MySQL| port would be used when port number isn't explicitly defined in the :variable:`wsrep_node_incoming_address`. Bug fixed :bug:`1082406` (*Alex Yurchenko*).
-
- Dropping a non-existing temporary table would be replicated when TOI was used in :variable:`wsrep_OSU_method` variable. This bug was fixed for the case when ``DROP TEMPORARY TABLE`` statement was used, but it will still replicate in case ``DROP TABLE`` statement is used on a temporary table. Bug fixed :bug:`1084702` (*Seppo Jaakola*).
-
- In case two nodes in a 3-node cluster had to abort due to inconsistency, one wouldn't correctly notify the surviving node which would lead to surviving node to loose the primary component and cause subsequent downtime. Bug fixed :bug:`1108165` (*Alex Yurchenko*).
-
- In some cases non-uniform foreign key reference could cause a slave crash. Fixed by using primary key of the child table when appending exclusive key for cascading delete operation. Bug fixed :bug:`1089490` (*Seppo Jaakola*).
-
- Parallel applying would fail in case mixed ``CHAR`` and ``VARCHAR`` columns would be used in foreign key definitions. Bug fixed :bug:`1100496` (*Seppo Jaakola*).
-
- *Debian* packages included the old version of **innotop**. Fixed by removing **innotop** and its ``InnoDBParser`` Perl package from source and *Debian* installation. Bug fixed :bug:`1032139` (*Alexey Bychko*).
-
- The mysqld_safe script would fail to retrieve the galera replication position on ``Ubuntu`` 10.04, because the different shell was used. Bug fixed :bug:`1108431` (*Alex Yurchenko*).
-
- Cascading foreign key constraint could lead to unresolved replication conflict and leave a slave hanging. Bug fixed :bug:`1130888` (*Seppo Jaakola*).
-
- If |MySQL| replication threads were started before running wsrep recovery, this would lead to memory corruption and server crash. Bug fixed :bug:`1132974` (*Seppo Jaakola*).
-
- Conflicting prepared statements in multi-master use case could cause node to hang. This was happening due to prepared statement execution loop, which does not honor wsrep status codes correctly. Bug fixed :bug:`1144911` (*Seppo Jaakola*).
-
- :ref:`state_snapshot_transfer` with |Xtrabackup| would fail if the ``tmpdir`` was specified more than once in the |MySQL| configuration file (:file:`my.cnf`). Bugs fixed :bug:`1160047` and :bug:`1086978` (*Raghavendra D Prabhu*).
-
- Issues with compiling Galera on the ``ARM`` architecture has been fixed. Bug fixed :bug:`1133047` (*Alex Yurchenko*).
-
- Upstream bugfix for bug :mysqlbug:`59354` triggered a regression that could cause transaction conflicts. Bug fixed :bug:`1158221` (*Seppo Jaakola*).
-
- Galera builds would fail when they were built with the new ``boost`` library. Bug fixed :bug:`1131736` (*Alex Yurchenko*).
-
- Folder ``lost+found`` wasn't included in the rsync SST filter, which caused the SST failure due to insufficient privileges. Fixed by excluding ``lost+found`` folder if found. Bug fixed :bug:`1154095` (*Alex Yurchenko*).
-
- If variable :variable:`innodb_thread_concurrency` has been defined to throttle |InnoDB| access, and work load contained DDL statements, a cluster node could remain hanging for unresolved MDL conflict. Fixed by adding a new method to cancel a thread waiting for |InnoDB| concurrency. Bug fixed :bug:`1155183` (*Seppo Jaakola*).
-
- Handling of the network issues in Galera has been improved. Bug fixed :bug:`1153727` (*Teemu Ollakka*).
-
- Fixed the wrong path in the ``/etc/xinetd.d/mysqlchk`` script. Bugs fixed :bug:`1000761` and :bug:`1132934` (*Raghavendra D Prabhu*).
-
- When upgrading the Percona-XtraDB-Cluster-server package, ``/usr/bin/clustercheck`` would get overwritten, and any changes (such as username and password) would be lost. Bug fixed :bug:`1158443` (*Raghavendra D Prabhu*).
-
- In case ``CREATE TABLE AS SELECT`` statement was running in parallel with the DDL statement on the selected table, in some cases first statement could be left hanging. Bug fixed :bug:`1164893` (*Seppo Jaakola*).
-
- Galera builds would fail when ``gcc`` 4.8 was used. Bug fixed :bug:`1164992` (*Alex Yurchenko*).
-
- ``Percona-XtraDB-Cluster-galera`` package version number didn't match the :variable:`wsrep_provider_version` one. Bug fixed :bug:`1111672` (*Alexey Bychko*).
-
- Only ``rpm`` debug build was available for |Percona XtraDB Cluster|, fixed by providing the ``deb`` debug build as well. Bug fixed :bug:`1096123` (*Ignacio Nin*).
- 
-Other bug fixes: bug fixed :bug:`1162421` (*Seppo Jaakola*), bug fixed :bug:`1093054` (*Alex Yurchenko*), bug fixed :bug:`1166060` (*Teemu Ollakka*), bug fixed :bug:`1166065` (*Teemu Ollakka*).
-
-Based on `Percona Server 5.5.30-30.2 <http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.30-30.2.html>`_ including all the bug fixes in it and on `Codership wsrep API 5.5.30-23.7.4 <https://launchpad.net/codership-mysql/+milestone/5.5.30-23.7.4>`_, |Percona XtraDB Cluster| 5.5.30-23.7.4 is now the current stable release. All of |Percona|'s software is open-source and free. 
-
 
=== removed file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.31-23.7.5.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.31-23.7.5.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.5.31-23.7.5.rst	1970-01-01 00:00:00 +0000
@@ -1,73 +0,0 @@
-.. rn:: 5.5.31-23.7.5
-
-========================================
- |Percona XtraDB Cluster| 5.5.31-23.7.5
-========================================
-
-Percona is glad to announce the release of |Percona XtraDB Cluster| on June 24th, 2013. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster/5.5.31-23.7.5/>`_ or from our :doc:`software repositories </installation>`.
-
-This is an General Availability release. We did our best to eliminate bugs and problems during the testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_.
-
-New Features
-============
-
- Information about the wsrep sequence number has been added to ``INFORMATION_SCHEMA`` :table:`INNODB_TRX` table.
-
- |Percona XtraDB Cluster| can now be :ref:`bootstrapped <bootstrap>` with the new ``bootstrap-pxc`` option in the init script.
-
- |Percona XtraDB Cluster| has implemented  parallel copying for rsync :ref:`state_snapshot_transfer` method. Bug fixed :bug:`1167331` (*Mrten*).
-
- |Percona XtraDB Cluster| has implemented new *Python* version of the `clustercheck <https://github.com/Oneiroi/clustercheck>`_ script.
-
- |Percona XtraDB Cluster| now has better integration with |Percona XtraBackup| 2.1 by implementing new ``xbstream`` option for xtrabackup :ref:`state_snapshot_transfer` method.
-
-
-Bugs fixed 
-==========
-
- Fixed the packaging issues that caused |Percona XtraDB Cluster| to conflict with |MySQL| libraries when performing fresh *CentOS* installation. Bug fixed :bug:`1183669`.
-
- The RPM installer script had the :term:`datadir` hardcoded to :file:`/var/lib/mysql` instead of ``using my_print_defaults`` to get the datadir info. bug fixed :bug:`1172621`.
-
- Fixed the package conflict for ``percona-xtradb-cluster-client-5.5`` package. Bug fixed :bug:`1172621`.
-
- Fixed the ``Percona-Server-shared-55`` and ``Percona-XtraDB-Cluster-shared`` ``RPM`` package dependences. Bug fixed :bug:`1050654`.
-
- ``mysql_tzinfo_to_sql`` script failed with |Percona XtraDB Cluster| since |MyISAM| DDL/DML were not consistently replicated. Fixed by enabling session variable :variable:`wsrep_replicate_myisam` in the generator file. Bug fixed :bug:`1161432`.
-
- Startup script on *Debian* and *Ubuntu* was failing prematurely during ``SST``. Bug fixed :bug:`1099428`.
-
- Due to *Debian* way of stopping/reloading/status checking, there was failure after SST since the machine-specific *Debian* maintenance password didn't work. Fixes by using signals instead of ``mysqladmin`` as it is done in *CentOS*. Bug fixed :bug:`1098360`.
-
- :variable:`wsrep-recover` would create ``ibdata1`` and ``ib_logfile*`` files which the SST after that would remove. Bug fixed :bug:`1191767`. 
-
- When running :variable:`wsrep_recover` to recover galera co-ordinates, LRU recover (and its blocking counterpart) were causing issues. Bug fixed :bug:`1108035`.
-
- |Percona XtraDB Cluster| improved status visibility in the ``processlist`` on other nodes when provider is locked with ``FLUSH TABLES WITH READ LOCK`` on one of them. Bug fixed :bug:`1109341`.
-
-Crash/stalling bugs
-------------------- 
-
- |Percona Server| `Crash-Resistant Replication <http://www.percona.com/doc/percona-server/5.5/reliability/crash_resistant_replication.html>`_ was causing conflicts with :variable:`wsrep_crash_recovery` on a node which is a slave to an async master in standard |MySQL| replication. Bugs fixed :bug:`1182441` and :bug:`1180802`.
- 
- |Percona XtraDB Cluster| node would hang on shutdown when :variable:`thread_handling` was set to  `pool-of-threads <http://www.percona.com/doc/percona-server/5.5/performance/threadpool.html#thread-pool>`_. Bug Fixed :bug:`1185523`.  
-
- ``FLUSH TABLES WITH READ LOCK`` didn't behave as expected, it had different behavior than the upstream |MySQL| version. Bug fixed :bug:`1170821`.
-
- When rsync :ref:`state_snapshot_transfer` failed, the rsync daemon would remain running which caused ``pid`` errors on subsequent ``SST`` retries. Bug fixed :bug:`1169676`.
-
- When doing cascading Foreign Key processing |Percona XtraDB Cluster| was doing unnecessary Foreign Key checks, which are needed only for the purpose of getting Foreign Key parent reference for child table modifications. Bug fixed :bug:`1134892`.
-
- High priority threads (slave threads, replaying threads, total order isolation threads) were not protected from kill signal and attempt to kill high priority thread could cause server to hang. Bug fixed :bug:`1088267`.
-
- Galera provider may deadlock if applier thread is still executing ``apply_trx()`` while processing commit, it could cause corresponding transaction to be purged from cert index.
-
-Regressions
------------
-
- Previous |Percona XtraDB Cluster| release introduced the regression in the RPM packaging that prevented the server from restarting following an upgrade. Bug fixed :bug:`1168032`. 
- 
-Other bug fixes: bug fixed :bug:`1187526`, bug fixed :bug:`1133266`, bug fixed :bug:`1079688`, bug fixed :bug:`1177211`, bug fixed :bug:`1166423`, bug fixed :bug:`1084573`, bug fixed :bug:`1069829`, bug fixed :bug:`1012138`, bug fixed :bug:`1170066`, bug fixed :bug:`1170706`, bug fixed :bug:`1182187`, bug fixed :bug:`1183530`, bug fixed :bug:`1183997`, bug fixed :bug:`1184034`, bug fixed :bug:`1191763`, bug fixed :bug:`1069829`.
-
-Based on `Percona Server 5.5.31-30.3 <http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.31-30.3.html>`_ including all the bug fixes in it and on `Codership wsrep API 5.5.31-23.7.5 <https://launchpad.net/codership-mysql/+milestone/5.5.31-23.7.5>`_, |Percona XtraDB Cluster| `5.5.31-23.7.5 <https://launchpad.net/percona-xtradb-cluster/+milestone/5.5.31-23.7.5>`_ is now the current stable release. All of |Percona|'s software is open-source and free. 
-
 
=== added file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.14-25.1.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.14-25.1.rst	1970-01-01 00:00:00 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.14-25.1.rst	2013-11-21 11:30:55 +0000
@@ -0,0 +1,78 @@
+.. rn:: 5.6.14-25.1
+
+======================================
+ |Percona XtraDB Cluster| 5.6.14-25.1
+======================================
+
+Percona is glad to announce the first Beta release of |Percona XtraDB Cluster| 5.6 on November 21st, 2013. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster/5.6.14-25.1/>`_ or from our :doc:`software repositories </installation>`.
+
+Based on `Percona Server 5.6.14-62.0 <http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.14-62.0.html>`_ including all the bug fixes in it, `Galera Replicator 3.1 <https://launchpad.net/galera/3.x/25.3.1>`_ and on `Codership wsrep API 5.6.14-25.1 <https://launchpad.net/codership-mysql/5.6/5.6.14-25.1>`_ is now the first **BETA** release. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.6.14-25.1 milestone <https://launchpad.net/percona-xtradb-cluster/+milestone/5.6.14-25.1>`_ at Launchpad.
+
+This release contains all of the features and bug fixes in `Percona XtraDB Cluster 5.5.34-23.7.6 <http://www.percona.com/doc/percona-xtradb-cluster/release-notes/Percona-XtraDB-Cluster-5.5.34-23.7.6.html>`_, plus the following:
+
+New Features
+============
+
+ |Percona XtraDB Cluster| is now using `Galera Replicator 3.1 <https://launchpad.net/galera/3.x/25.3.1>`_ and `Codership wsrep API 5.6.14-25.1 <https://launchpad.net/codership-mysql/5.6/5.6.14-25.1>`_.
+
+ |Percona XtraDB Cluster| has implemented a number of `XtraDB performance improvements <http://www.percona.com/doc/percona-server/5.6/performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.html>`_ for I/O-bound high-concurrency workloads. 
+
+ |Percona XtraDB Cluster| has implemented a number of performance improvements for `Page cleaner thread tuning <http://www.percona.com/doc/percona-server/5.6/performance/page_cleaner_tuning.html#page-cleaner-tuning>`_. 
+
+ ``ALL_O_DIRECT`` method for `innodb_flush_method <http://www.percona.com/doc/percona-server/5.6/scalability/innodb_io.html#innodb_flush_method>`_ has been ported from 5.5 version.
+
+ `Statement Timeout <http://www.percona.com/doc/percona-server/5.6/management/statement_timeout.html#statement-timeout>`_ feature has been ported from the Twitter branch.
+
+ |Percona XtraDB Cluster| has `extended <http://www.percona.com/doc/percona-server/5.6/flexibility/extended_select_into_outfile.html#extended-select-into-outfile>`_ the ``SELECT INTO ... OUTFILE`` and ``SELECT INTO DUMPFILE`` to add the support for ``UNIX`` sockets and named pipes.
+
+ |Percona XtraDB Cluster| has implemented more efficient log block checksums with new `innodb_log_checksum_algorithm <http://www.percona.com/doc/percona-server/5.6/scalability/innodb_io.html#innodb_log_checksum_algorithm>`_ variable.
+
+ |Percona XtraDB Cluster| now supports `Per-query variable statements <http://www.percona.com/doc/percona-server/5.6/flexibility/per_query_variable_statement.html#per-query-variable-statement>`_.
+
+ Limited support for Query Cache has been implemented. Query cache cannot still be fully enabled during the startup. To enable query cache, ``mysqld`` should be started with ``query_cache_type=1`` and ``query_cache_size=0`` and then query_cache_size should be changed to desired value during runtime.
+
+ ``RPM`` packages are now made `relocatable <http://rpm5.org/docs/api/relocatable.html>`_ which means they now support installation to custom prefixes.
+
+Bugs fixed 
+==========
+
+ Some wsrep variables (:variable:`wsrep_provider`, :variable:`wsrep_provider_options`, :variable:`wsrep_cluster_address`...) could be "doubly" allocated which caused memory leaks. Bug fixed :bug:`1072839`.
+ 
+ If ``SELECT FOR UPDATE...`` query was aborted due to multi-master conflict, the client wouldn't get back the deadlock error. From client perspective the transaction would be successful. Bug fixed :bug:`1187739`.
+
+ Temporary tables are not replicated, but any DDL on those tables were, which would generates error messages on other nodes. Bugs fixed :bug:`1194156`, :bug:`1084702`, :bug:`1212247`.
+
+ When setting the :variable:`gcache.size` to a larger value than the default 128M, the mysql service command did not allow enough time for the file to be preallocated. Bug fixed :bug:`1207500`.
+ 
+ When installing first ``Percona-XtraDB-Cluster-client`` and then ``Percona-XtraDB-Cluster-server`` on two single statements or a single statement with both packages , yum would install ``percona-xtrabackup-20`` instead ``percona-xtrabackup`` package as dependency of ``Percona-XtraDB-Cluster-server``. Bug fixed :bug:`1226185`.
+
+ Different mutex implementation in the 5.6 could lead to server assertion error. Bug fixed :bug:`1233383`.
+
+ Enabling :variable:`wsrep_log_conflicts` variable could cause issues with ``lock_mutex``. Bug fixed :bug:`1234382`.
+
+ Server could freeze with mixed DML/DDL load because TOI brute force aborts were not properly propagated. Bug fixed :bug:`1239571`.
+
+ ``CREATE TABLE AS SELECT`` would fail with explicit temporary tables, when was binlogging enabled and :variable:`autocommit` was set to ``0``. Bug fixed :bug:`1240098`.
+
+ Transaction cleanup function did not get called for autocommit statements after rollback, it would stay in ``LOCAL_COMMIT`` even after rollback finished which caused problems when the next transaction started. Bug fixed :bug:`1240567`.
+
+ ``DDL`` statements like ``CREATE TEMPORARY TABLE LIKE`` would be replicated and applied in all cluster nodes. This caused temporary table definitions to pile up in slave threads. Bug fixed :bug:`1246257`.
+ 
+ ``CREATE TABLE AS SELECT`` was not replicated, if the select result set was empty. Bug fixed :bug:`1246921`.
+
+ Write set flags defined in wsrep API are now exposed to application side appliers too. Bug fixed :bug:`1247402`.
+
+ Local brute force aborts are counted accurately. Bug fixed :bug:`1247971`.
+
+ Certain combinations of transaction rollbacks could leave stale transactional ``MDL`` locks. Bug fixed :bug:`1247978`. 
+
+ After turning ``UNIV_SYNC_DEBUG`` on, node that was started from clean state would crash immediately at startup. Bug fixed :bug:`1248908`.
+ 
+ Server built with ``UNIV_SYNC_DEBUG`` would assert if SQL load has ``DELETE`` statements on tables with foreign key constraints with ``ON DELETE CASCADE`` option. Bug fixed :bug:`1248921`.
+
+ Xtrabackup SST dependencies have been added as Optional/Recommended/Suggested dependencies. Bug fixed :bug:`1250326`.
+
+Other bugs fixed: bug fixed :bug:`1020457`, bug fixed :bug:`1250865`, bug fixed :bug:`1249753`, bug fixed :bug:`1248396`, bug fixed :bug:`1247980`, bug fixed :bug:`1238278`, bug fixed :bug:`1234421`, bug fixed :bug:`1228341`, bug fixed :bug:`1228333`, bug fixed :bug:`1225236`, bug fixed :bug:`1221354`, bug fixed :bug:`1217138`, bug fixed :bug:`1206648`, bug fixed :bug:`1200647`, bug fixed :bug:`1180792`, bug fixed :bug:`1163283`, bug fixed :bug:`1234229`, bugs fixed :bug:`1250805`, bug fixed :bug:`1233301`, and bug fixed :bug:`1210509`.
+
+We did our best to eliminate bugs and problems during the testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our `bug tracking system <https://bugs.launchpad.net/percona-xtradb-cluster/+filebug>`_.
+
 
=== modified file 'doc-pxc/source/release-notes/release-notes_index.rst'
--- doc-pxc/source/release-notes/release-notes_index.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/release-notes/release-notes_index.rst	2013-11-21 11:30:55 +0000
@@ -1,17 +1,9 @@
-======================================
-|Percona XtraDB Cluster| Release notes
-======================================
+============================================
+ |Percona XtraDB Cluster| 5.6 Release notes
+============================================
 
 .. toctree::
    :maxdepth: 1
    :glob:
 
-   Percona-XtraDB-Cluster-5.5.31-23.7.5
-   Percona-XtraDB-Cluster-5.5.30-23.7.4
-   Percona-XtraDB-Cluster-5.5.29-23.7.2
-   Percona-XtraDB-Cluster-5.5.29
-   Percona-XtraDB-Cluster-5.5.28
-   Percona-XtraDB-Cluster-5.5.27
-   Percona-XtraDB-Cluster-5.5.24
-   Percona-XtraDB-Cluster-5.5.23
-
+   Percona-XtraDB-Cluster-5.6.14-25.1
 
=== added file 'doc-pxc/source/upgrading_guide_55_56.rst'
--- doc-pxc/source/upgrading_guide_55_56.rst	1970-01-01 00:00:00 +0000
+++ doc-pxc/source/upgrading_guide_55_56.rst	2013-11-21 11:30:55 +0000
@@ -0,0 +1,119 @@
+.. _upgrading_guide:
+
+==================================================================
+ Percona XtraDB Cluster In-Place Upgrading Guide: From 5.5 to 5.6
+==================================================================
+
+Upgrading cluster involves two major stages:
+
+I) Upgrade a single node
+II) Upgrade the whole cluster while not breaking replication
+ 
+Following is the upgrade process on CentOS 6.4
+==============================================
+ 
+**Step #1** Make sure all the nodes in cluster are upgraded to the latest 5.5 version and are in synced state.
+ 
+Stage I 
+--------
+Assuming we are going to upgrade node A, (and other nodes B and C are on 5.5)
+ 
+**Step #2** On node A stop the mysql process and remove the old packages: ::
+
+    # service mysql stop
+    # yum remove 'Percona*'
+ 
+**Step #3** Install the new packages: ::
+
+    # yum install Percona-XtraDB-Cluster-server-56 Percona-XtraDB-Cluster-client-56 percona-xtrabackup
+ 
+**Step #4** Fix the variables in the |MySQL| configuration file :file:`my.cnf` which are not compatible with |Percona Server| 5.6. Detailed list can be checked in `Changed in Percona Server 5.6 <http://www.percona.com/doc/percona-server/5.6/changed_in_56.html>`_ documentation. Add the following to :file:`my.cnf` for compatibility with 5.5 replication for the duration of upgrade, add 'socket.checksum=1' to the :variable:`wsrep_provider_options` variable, and set the following options: ::
+
+    wsrep_provider_options="socket.checksum=1"
+    log_bin_use_v1_row_events=1
+    gtid_mode=0
+    binlog_checksum=NONE
+    wsrep-slave-threads=1
+    read_only=ON
+
+**Step #5** Next, start the node with the variable :variable:`wsrep_provider` set to ``none``: ::
+
+    # mysqld --skip-grant-tables --user=mysql --wsrep-provider='none' 
+ 
+This is to ensure that other hosts are not affected by this upgrade.
+ 
+**Step #6** While Step #5 is running, in the background or in another session run: ::
+
+    # mysql_upgrade
+ 
+**Step #7** Step #5 must complete successfully, upon which, process started in Step 5) can be stopped/killed.
+ 
+ 
+**Step #8** Step #5) should not fail (if it fails check for any bad variables in the configuration file), otherwise :file:`grastate.dat` can potentially get zeroed and the node will try to perform State Snapshot Transfer from a 5.5 node. ('Potentially' since with --wsrep-provider='none' it shouldn't). Also backing up :file:`grastate.dat` is recommended prior to Step #5 for the same purpose.
+
+**Step #9** If all the steps above have completed successfully node can be started with: ::
+  
+    # service mysql start 
+ 
+**Step #10** At this point, other nodes (B, C) should acknowledge that this node is up and synced! 
+
+Stage II
+---------
+ 
+**Step #11** After this has been set up all 5.5 nodes can be upgraded, one-by-one, as described in the Stage I. 
+
+  a) After all nodes in the cluster are upgraded to 5.6, option :variable:`read_only` should be set to ``OFF``. 
+
+  b) Nodes should be restarted with compatibility options added earlier removed/updated for optimal performance (though cluster will continue run with those options).
+ 
+Following is the upgrade process on Ubuntu 12.04 (precise)
+==========================================================
+
+**Step #1** Make sure all the nodes in cluster are upgraded to the latest 5.5 version and are in synced state.
+
+Stage I 
+--------
+Assuming we are going to upgrade node A, (and other nodes B and C are on 5.5)
+
+**Step #2** On node A stop the mysql process and remove the old packages: ::
+
+    # /etc/init.d/mysql stop
+    # apt-get remove percona-xtradb-cluster-server-5.5 percona-xtradb-cluster-galera-2.x percona-xtradb-cluster-common-5.5 percona-xtradb-cluster-client-5.5
+
+**Step #3** Fix the variables in the |MySQL| configuration file :file:`my.cnf` which are not compatible with |Percona Server| 5.6. Detailed list can be checked in `Changed in Percona Server 5.6 <http://www.percona.com/doc/percona-server/5.6/changed_in_56.html>`_ documentation. Add the following to :file:`my.cnf` for compatibility with 5.5 replication for the duration of upgrade, add 'socket.checksum=1' to the :variable:`wsrep_provider_options` variable and set :variable:`wsrep_provider` set to ``none`` ::
+
+    wsrep_provider_options="socket.checksum=1"
+    wsrep_provider=none
+    log_bin_use_v1_row_events=1
+    gtid_mode=0
+    binlog_checksum=NONE
+    wsrep-slave-threads=1
+
+**Step #4** Install the new packages: ::
+
+    # apt-get install percona-xtradb-cluster-server-5.6 percona-xtradb-cluster-client-5.6 percona-xtrabackup
+
+**Step #5** After node has been started you'll need to run ``mysql_upgrade``: ::
+
+    # mysql_upgrade
+
+**Step #6** Step #5) should not fail (if it fails check for any bad variables in the configuration file), otherwise :file:`grastate.dat` can potentially get zeroed and the node will try to perform State Snapshot Transfer from a 5.5 node. ('Potentially' since with --wsrep-provider='none' it shouldn't). Also backing up :file:`grastate.dat` is recommended prior to Step #5 for the same purpose.
+
+
+**Step #7** If all the steps above have completed successfully,  set the :variable:`wsrep_provider` to the location of the Galera library, and node can be started with: ::
+  
+    # service mysql start 
+
+**Step #8** At this point, other nodes (B, C) should acknowledge that this node is up and synced!
+
+Stage II
+---------
+
+**Step #9**   After this has been set up all 5.5 nodes can be upgraded, one-by-one, as described in the Stage I. 
+
+  a) After all nodes in the cluster are upgraded to 5.6, option :variable:`read_only` should be set to ``OFF``. 
+
+  b) Nodes should be restarted with compatibility options added earlier removed/updated for optimal performance (though cluster will continue run with those options).
+
+
+