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

[Hrvoje Matijakovic]

[Raghavendra D Prabhu (raghavendra-prabhu)]

+ /usr/bin/clustercheck clustercheck password 0

is fine. But mention this part:

        # <user> <pass> <available_when_donor=0|1> <log_file> <available_when_readonly=0|1> <defaults_extra_file>"
        # Recommended: server_args = user pass 1 /var/log/log-file 0 /etc/my.cnf.local"
        # Compatibility: server_args = user pass 1 /var/log/log-file 1 /etc/my.cnf.local"

+In CentOS ``mysql-libs`` conflicts with ``Percona-XtraDB-Cluster-server-56.x86_64`` package. To avoid this you can replace the ``mysql-libs`` with ``Percona-Server-shared-51.x86_64`` package.

To replace you need to remove mysql-libs (there is no 'replace' in yum) before installing PXC packages. Dependency resolution ensures -shared-51 is installed.

+ - 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.

Mention about wsrep_replicate_myisam here.

+Based on `Percona Server 5.6.15-63.0 <http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.15-63.0.html>`_ including all the bug fixes in it, `Galera Replicator 3.3 <https://launchpad.net/galera/+milestone/25.3.3>`_ and on `Codership wsrep API 5.6.15-25.2 <https://launchpad.net/codership-mysql/+milestone/5.6.15-25.2>`_ is now the first **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.15-25.5 milestone <https://launchpad.net/percona-xtradb-cluster/+milestone/5.6.15-25.5>`_ at Launchpad.

It is Galera 3.4 here. https://launchpad.net/galera/+milestone/25.3.4

Codership API 25.5 - https://launchpad.net/codership-mysql/+milestone/5.6.16-25.5

+ Bug fixed :bug:`1219605`.

Replication of partition tables without binlogging enabled
failed, partition truncation didn't work because of lack of TO
isolation there.

+ Bug fixed :bug:`1272982`.

Ignore this. :)

+ Bug fixed :bug:`1281682`.

New options (under [sst]) are added: inno-backup-opts, inno-apply-opts, inno-move-opts which pass options to backup, apply and move stages of innobackupex.

+ Using ``LOAD DATA INFILE`` in with :variable:`autocommit` set to ``0`` and :variable:`wsrep_load_data_splitting` set to ``ON`` could lead to data loss. Bug fixed :bug:`1281810`.

Let us not mention 'data loss' here. It was not that explicit of a loss. Instead, 'incomplete loading of records while chunking' would be better here.

+ Bug fixed :bug:`1284670`.

Not user visible, safe to skip (may cause unneeed alarm among users :)).

+ If a particular node was setup to be the donor via setting :variable:`wsrep_sst_donor` and the donor node was in desynced state for some reason, then the joiner would wait for the donor to become synced again which could take a long time. Bug fixed :bug:`1285380`.

This is a bit more complex. Best way to describe would be to say "The joiner would wait and not fall back to choosing other potential donor ...

review: Needs Fixing

[Raghavendra D Prabhu (raghavendra-prabhu)]

One more thing, for sst-initial-timeout, default is 100 seconds, a value of 0 disables this.

[Raghavendra D Prabhu (raghavendra-prabhu)]

+In CentOS ``mysql-libs`` conflicts with ``Percona-XtraDB-Cluster-server-56.x86_64`` package. To avoid this you need to remove the ``mysql-libs`` package before installing |Percona XtraDB Cluster|.

In addition, mention that -shared-51 package provides that
dependency during installation if required.

+ Bug fixed :bug:`1284670`.

Skip this (as mentioned before).

Others look good.

review: Approve

=== modified file 'doc-pxc/source/conf.py'
--- doc-pxc/source/conf.py	2014-02-20 10:50:23 +0000
+++ doc-pxc/source/conf.py	2014-03-20 09:44:42 +0000
@@ -55,7 +55,7 @@
 # The short X.Y version.
 version = '5.6.15'
 # The full version, including alpha/beta/rc tags.
-release = '5.6.15-25.4'
+release = '5.6.15-25.5'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

=== modified file 'doc-pxc/source/faq.rst'
--- doc-pxc/source/faq.rst	2013-09-05 13:37:01 +0000
+++ doc-pxc/source/faq.rst	2014-03-20 09:44:42 +0000
@@ -22,13 +22,51 @@
 
 .. code-block:: mysql
 
-    SELECT * FROM someinnodbtable WHERE id=1;
+   SELECT 1 FROM dual;
 
 3 different results are possible:
    * You get the row with id=1 (node is healthy)
    * Unknown error (node is online but Galera is not connected/synced with the cluster)
    * Connection error (node is not online)
 
+You can also check the node health with the ``clustercheck`` script. You need to set up ``clustercheck`` user:
+
+.. code-block:: mysql
+
+   GRANT USAGE ON *.* TO 'clustercheck'@'localhost' IDENTIFIED BY PASSWORD '*2470C0C06DEE42FD1618BB99005ADCA2EC9D1E19';
+
+You can then check the node health by running the ``clustercheck`` script: 
+
+.. code-block:: bash
+
+   /usr/bin/clustercheck clustercheck password 0
+
+If the node is running correctly you should get the following status: :: 
+
+  HTTP/1.1 200 OK
+  Content-Type: text/plain
+  Connection: close
+  Content-Length: 40
+
+  Percona XtraDB Cluster Node is synced.
+
+In case node isn't sync or if it is off-line status will look like: :: 
+
+  HTTP/1.1 503 Service Unavailable
+  Content-Type: text/plain
+  Connection: close
+  Content-Length: 44
+
+  Percona XtraDB Cluster Node is not synced. 
+
+.. note::
+
+   clustercheck syntax: 
+
+   <user> <pass> <available_when_donor=0|1> <log_file> <available_when_readonly=0|1> <defaults_extra_file>"
+   Recommended: server_args = user pass 1 /var/log/log-file 0 /etc/my.cnf.local"
+   Compatibility: server_args = user pass 1 /var/log/log-file 1 /etc/my.cnf.local"
+
 Q: How does XtraDB Cluster handle big transaction?
 ==================================================
 A: XtraDB Cluster populates write set in memory before replication and this sets one limit for how large transactions make sense. There are wsrep variables for max row count and max size of of write set to make sure that server is not running out of memory.

=== modified file 'doc-pxc/source/index.rst'
--- doc-pxc/source/index.rst	2014-01-30 13:23:38 +0000
+++ doc-pxc/source/index.rst	2014-03-20 09:44:42 +0000
@@ -99,6 +99,7 @@
    release-notes/release-notes_index
    wsrep-status-index
    wsrep-system-index
+   wsrep-provider-index
    wsrep-files-index
    faq
    glossary

=== modified file 'doc-pxc/source/installation/yum_repo.rst'
--- doc-pxc/source/installation/yum_repo.rst	2014-01-29 15:10:12 +0000
+++ doc-pxc/source/installation/yum_repo.rst	2014-03-20 09:44:42 +0000
@@ -38,7 +38,7 @@
 
 .. warning:: 
 
-   In order to sucessfully install |Percona XtraDB Cluster| ``socat`` package will need to be installed first.
+   In order to sucessfully install |Percona XtraDB Cluster| ``socat`` package will need to be installed first. ``socat`` package can be installed from the `EPEL <https://fedoraproject.org/wiki/EPEL>`_ repositories.
 
 
 Percona `yum` Experimental repository
@@ -50,3 +50,8 @@
 
 .. note:: 
  This repository works for both RHEL/CentOS 5 and RHEL/CentOS 6
+
+Resolving package conflicts
+===========================
+
+In CentOS ``mysql-libs`` conflicts with ``Percona-XtraDB-Cluster-server-56.x86_64`` package. To avoid this you need to remove the ``mysql-libs`` package before installing |Percona XtraDB Cluster|. Package ``Percona-Server-shared-51.x86_64`` provides that dependency during installation if required.

=== modified file 'doc-pxc/source/intro.rst'
--- doc-pxc/source/intro.rst	2014-01-29 15:10:12 +0000
+++ doc-pxc/source/intro.rst	2014-03-20 09:44:42 +0000
@@ -44,7 +44,7 @@
 
 |Percona XtraDB Cluster| has: Consistency and Availability.
 
-That is |MySQL| replication does not guarantee Consistency of your data, while |Percona XtraDB Cluster| provides data Consistency (but it looses Partitioning tolerance property).
+That is |MySQL| replication does not guarantee Consistency of your data, while |Percona XtraDB Cluster| provides data Consistency (but it loses Partitioning tolerance property).
 
 Components
 ==========

=== modified file 'doc-pxc/source/limitation.rst'
--- doc-pxc/source/limitation.rst	2013-11-21 11:29:19 +0000
+++ doc-pxc/source/limitation.rst	2014-03-20 09:44:42 +0000
@@ -6,7 +6,7 @@
 
 There are some limitations which you should be aware of. Some of them will be eliminated later as product is improved and some are design limitations.
 
- - 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.
+ - 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. You can enable experimental |MyISAM| replication support with :variable:`wsrep_replicate_myisam`.
 
  - Unsupported queries:
 

=== modified file 'doc-pxc/source/manual/xtrabackup_sst.rst'
--- doc-pxc/source/manual/xtrabackup_sst.rst	2014-02-20 09:44:18 +0000
+++ doc-pxc/source/manual/xtrabackup_sst.rst	2014-03-20 09:44:42 +0000
@@ -166,6 +166,13 @@
  
 This option introduces stream-based compression/decompression. When these options are set, compression/decompression are done on stream, in contrast to earlier PXB-based one where decompression was done after streaming to disk, involving additional I/O; hence I/O is saved here (almost halved on joiner). You can use any compression utility which works on stream - gzip, pigz (which is multi-threaded and hence, recommended) etc. Also, note that, compressor has to be set on donor and decompressor on joiner (though you can have decompressor set on donor and vice-versa for config homogeneity, it won't affect that particular SST). To use Xtrabackup-based compression as before use ``compress`` under ``[xtrabackup]`` as before, also having both enabled won't cause any failure (though you will be wasting CPU cycles with this).
 
+.. option:: sst-initial-timeout
+   
+   :Values: 0 (Disabled)
+   :Default: 100
+
+This option is use to configure initial timeout to receive a first packet via SST. This has been implemented, so that if donor dies somewhere in between, joiner doesn't hang.
+
 .. _tar_ag_xbstream:
 
 Tar against xbstream

=== added file 'doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.15-25.5.rst'
--- doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.15-25.5.rst	1970-01-01 00:00:00 +0000
+++ doc-pxc/source/release-notes/Percona-XtraDB-Cluster-5.6.15-25.5.rst	2014-03-20 09:44:42 +0000
@@ -0,0 +1,54 @@
+.. rn:: 5.6.15-25.5
+
+======================================
+ |Percona XtraDB Cluster| 5.6.15-25.5
+======================================
+
+Percona is glad to announce the release of |Percona XtraDB Cluster| 5.6 on March 20th 2014. Binaries are available from `downloads area <http://www.percona.com/downloads/Percona-XtraDB-Cluster-56/release-5.6.15-25.5/>`_ or from our :doc:`software repositories </installation>`.
+
+Based on `Percona Server 5.6.15-63.0 <http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.15-63.0.html>`_ including all the bug fixes in it, `Galera Replicator 3.4 <https://launchpad.net/galera/+milestone/25.3.4>`_ and on `Codership wsrep API 25.5 <https://launchpad.net/codership-mysql/+milestone/5.6.16-25.5>`_ 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.15-25.5 milestone <https://launchpad.net/percona-xtradb-cluster/+milestone/5.6.15-25.5>`_ at Launchpad.
+
+
+Bugs fixed 
+==========
+
+ Replication of partition tables without binlogging enabled failed, partition truncation didn't work because of lack of TO isolation there. Bug fixed :bug:`1219605`.
+
+ wsrep patch did not allow server to start with query cache enabled. This restriction and check have been removed now and query cache can be fully enabled from config file. Bug fixed :bug:`1279220`.
+
+ New SST options have been implemented: :option:`inno-backup-opts`, :option:`inno-apply-opts`, :option:`inno-move-opts` which pass options to backup, apply and move stages of innobackupex. Bug fixed :bug:`1281682`.
+
+ Using ``LOAD DATA INFILE`` in with :variable:`autocommit` set to ``0`` and :variable:`wsrep_load_data_splitting` set to ``ON`` could lead to incomplete loading of records while chunking. Bug fixed :bug:`1281810`.
+
+ ``Garbd`` could crash on *CentOS* if variable :variable:`gmcast.listen_addr` wasn't set. Bug fixed :bug:`1283100`.
+
+ Node couldn't be started with :variable:`wsrep_provider_options` option :variable:`debug` set to ``1``. Bug fixed :bug:`1285208`. 
+
+ The joiner would wait and not fall back to choosing other potential donor nodes (not listed in :variable:`wsrep_sst_donor`) by their state. This happened even when comma was added at the end. This fixes it for that particular case. Bug fixed :bug:`1285380`.
+
+ Boostrapping a Node in a ``NON-PRIMARY`` state would lead to crash. Bug fixed :bug:`1286450`.
+
+ New versions of xtrabackup SST scripts were ignoring ``--socket`` parameter passed by mysqld. Bug fixed :bug:`1289483`.
+
+ Regression in Galera required explicitly setting :variable:`socket.ssl` to ``Yes`` even if you set up variables :variable:`socket.ssl_key` and :variable:`socket.ssl_cert`. Bug fixed :bug:`1290006`.
+
+ Fixed the ``clang`` build issues that were happening during the Galera build. Bug fixed :bug:`1290462`.
+
+ Initial configurable timeout, of 100 seconds, to receive a first packet via SST has been implemented, so that if donor dies somewhere in between, joiner doesn't hang. Timeout can be configured with the :option:`sst-initial-timeout` variable. Bug fixed :bug:`1292991`.
+
+ Better diagnostic error message has been implemented when :variable:`wsrep_max_ws_size` limit has been succeeded. Bug fixed :bug:`1280557`.
+
+ Fixed incorrect warnings and implemented better handling of repeated usage with same value for :variable:`wsrep_desync`. Bug fixed :bug:`1281696`.
+
+ Fixed the issue with :variable:`wsrep_slave_threads` wherein if the number of slave threads was changed before closing threads from an earlier change, it could increase the total number of threads beyond value specified in :variable:`wsrep_slave_threads`.
+
+ A regression in mutex handling caused dynamic update of :variable:`wsrep_log_conflicts` to hang the server. Bug fixed :bug:`1293624`.
+
+ Presence of :file:`/tmp/test` directory and an empty test database caused |Percona Xtrabackup| to fail, causing SST to fail. This is an |Percona XtraBackup| issue. But, this has been fixed in PXC's xtrabackup SST separately by using unique temporary directories with |Percona Xtrabackup|. Bug fixed :bug:`1294760`.
+
+ After installing the ``auth_socket`` plugin any local user might get root access to the server. If you're using this plugin upgrade is advised. This is a regression, introduced in |Percona Server| :rn:`5.6.11-60.3`. Bug fixed :bug:`1289599`
+
+Other bug fixes: :bug:`1289776`, :bug:`1279343`, :bug:`1259649`, :bug:`1292533`, :bug:`1272982`, :bug:`1284670`
+
+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	2014-02-20 10:50:23 +0000
+++ doc-pxc/source/release-notes/release-notes_index.rst	2014-03-20 09:44:42 +0000
@@ -6,6 +6,7 @@
    :maxdepth: 1
    :glob:
 
+   Percona-XtraDB-Cluster-5.6.15-25.5
    Percona-XtraDB-Cluster-5.6.15-25.4
    Percona-XtraDB-Cluster-5.6.15-25.3
    Percona-XtraDB-Cluster-5.6.15-25.2

=== added file 'doc-pxc/source/wsrep-provider-index.rst'
--- doc-pxc/source/wsrep-provider-index.rst	1970-01-01 00:00:00 +0000
+++ doc-pxc/source/wsrep-provider-index.rst	2014-03-20 09:44:42 +0000
@@ -0,0 +1,638 @@
+.. _wsrep_provider_index:
+
+============================================
+ Index of :variable:`wsrep_provider` options
+============================================
+
+Following variables can be set and checked in the :variable:`wsrep_provider_options` variable. Value of the variable can be changed in the |MySQL| configuration file, :file:`my.cnf`, or by setting the variable value in the |MySQL| client.
+
+To change the value of the in the :file:`my.cnf` following syntax should be used: :: 
+
+  wsrep_provider_options="variable1=value1;[variable2=value2]"
+
+For example to increase the size of the Galera buffer storage from the default value to 512MB, :file:`my.cnf` option should look like: ::
+
+  wsrep_provider_options="gcache.size=512M"
+
+Dynamic variables can be changed from the |MySQL| client by using the ``SET GLOBAL`` syntax. To change the value of the :variable:`pc.ignore_sb` following command should be used:: 
+
+  mysql> SET GLOBAL wsrep_provider_options="pc.ignore_sb=true";
+
+
+Index
+=====
+
+.. variable:: base_host
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: value of the :variable:`wsrep_node_address`
+
+This variable sets the value of the node's base IP. This is an IP address on which Galera listens for connections from other nodes. Setting this value incorrectly would stop the node from communicating with other nodes.
+
+.. variable:: base_port
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 4567
+
+This variable sets the port on which the Galera listens for connections from other nodes. Setting this value incorrectly would stop the node from communicating with other nodes.
+
+.. variable:: cert.log_conflicts
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: no
+
+.. variable:: evs.causal_keepalive_period
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: value of :variable:`evs.keepalive_period`
+
+This variable is used for development purposes and shouldn't be used by regular users. 
+
+.. variable:: evs.debug_log_mask
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: 0x1
+
+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.inactive_check_period
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: PT0.5S
+
+This variable defines how often to check for peer inactivity.
+
+.. variable:: evs.inactive_timeout
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: PT15S
+
+This variable defines the inactivity limit, once this limit is reached the node will be pronounced dead.
+
+.. variable:: evs.info_log_mask
+
+   :cli: No
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0
+
+This variable is used for controlling the extra EVS info logging.
+
+.. variable:: evs.install_timeout
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: PT15S
+
+This variable defines the timeout on waiting for install message acknowledgments.
+
+.. variable:: evs.join_retrans_period
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: PT1S
+
+This variable defines how often to retransmit EVS join messages when forming cluster membership.
+
+.. variable:: evs.keepalive_period 
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: PT1S 
+
+This variable defines how often will keepalive beacons will be emmited (in the absence of any other traffic).
+
+.. variable:: evs.max_install_timeouts
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 1
+
+This variable defines how many membership install rounds to try before giving up (total rounds will be :variable:`evs.max_install_timeouts` + 2).
+
+.. variable:: evs.send_window
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 4
+
+This variable defines the maximum number of data packets in replication at a time. For WAN setups may be set considerably higher, e.g. 512. This variable must be no less than :variable:`evs.user_send_window`.
+
+.. variable:: evs.stats_report_period
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: PT1M 
+
+This variable defines the control period of EVS statistics reporting.
+
+.. variable:: evs.suspect_timeout
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: PT5S
+
+This variable defines the inactivity period after which the node is “suspected” to be dead. If all remaining nodes agree on that, the node will be dropped out of cluster even before :variable:`evs.inactive_timeout` is reached.
+
+.. variable:: evs.use_aggregate
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: true
+
+When this variable is enabled smaller packets will be aggregated into one.
+
+.. variable:: evs.user_send_window
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: 2
+
+This variable defines the maximum number of data packets in replication at a time. For WAN setups may be set considerably higher, e.g. 512.
+
+.. variable:: evs.version
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0
+
+.. variable:: evs.view_forget_timeout
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: P1D
+
+This variable defines the timeout after which past views will be dropped from history.
+
+.. variable:: gcache.dir
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: :term:`datadir`
+
+This variable can be used to define the location of the :file:`galera.cache` file.
+
+.. variable:: gcache.keep_pages_size
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Local, Global
+   :dyn: No
+   :default: 0
+
+This variable is used to specify total size of the page storage pages to keep for caching purposes. If only page storage is enabled, one page is always present.
+
+.. variable:: gcache.mem_size
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0
+
+
+.. variable:: gcache.name
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: /var/lib/mysql/galera.cache
+
+This variable can be used to specify the name of the Galera cache file.
+
+.. variable:: gcache.page_size
+
+   :cli: No
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 128M
+
+This variable can be used to specify the size of the page files in the page storage.
+
+.. variable:: gcache.size
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 128M
+
+Size of the transaction cache for Galera replication. This defines the size of the :file:`galera.cache` file which is used as source for |IST|. If this value is bigger there are better chances that the re-joining node will get IST instead of |SST|.
+
+.. variable:: gcs.fc_debug
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0
+
+This variable specifies after how many writesets the debug statistics about SST flow control will be posted.
+
+.. variable:: gcs.fc_factor
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 1
+
+This variable is used for replication flow control. Replication will be paused till the value of this variable goes below the value of :variable:`gcs.fc_factor` * :variable:`gcs.fc_limit`.
+
+.. variable:: gcs.fc_limit
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 16
+
+This variable is used for replication flow control. When slave queue exceeds this limit replication will be paused.
+
+.. variable:: gcs.fc_master_slave
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: NO
+
+This variable is used to specify if there is only one master node in the cluster.
+
+.. variable:: gcs.max_packet_size
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 64500
+
+This variable is used to specify the writeset size after which they will be fragmented.
+
+.. variable:: gcs.max_throttle
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0.25
+
+This variable specifies how much the replication can be throttled during the state transfer in order to avoid running out of memory. Value can be set to ``0.0`` if stopping replication is acceptable in order to finish state transfer.
+ 
+.. variable:: gcs.recv_q_hard_limit
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 9223372036854775807
+
+This variable specifies the maximum allowed size of the receive queue. This should normally be half of (RAM + swap). If this limit is exceeded, Galera will abort the server.
+
+.. variable:: gcs.recv_q_soft_limit
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0.25
+
+This variable specifies the fraction of the :variable:`gcs.recv_q_hard_limit` after which replication rate will be throttled.
+
+.. variable:: gcs.sync_donor
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: NO
+
+This variable controls if the rest of the cluster should be in sync with the donor node. When this variable is set to ``Yes`` whole cluster will be blocked if the donor node is blocked with SST.
+
+.. variable:: gmcast.listen_addr
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: tcp://0.0.0.0:4567
+
+This variable defines the address on which node listens to connections from other nodes in the cluster.
+
+.. variable:: gmcast.mcast_addr
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: None
+
+This variable should be set up if UDP multicast should be used for replication.
+
+.. variable:: gmcast.mcast_ttl
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 1
+
+This variable can be used to define TTL for multicast packets.
+
+.. variable:: gmcast.peer_timeout
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: PT3S
+
+This variable specifies the connection timeout to initiate message relaying.
+
+.. variable:: gmcast.segment
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0
+
+This variable specifies the group segment this member should be a part of. Same segment members are treated as equally physically close.
+
+.. variable:: gmcast.time_wait
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: PT5S
+
+This variable specifies the time to wait until allowing peer declared outside of stable view to reconnect.
+
+.. variable:: gmcast.version
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0
+
+.. variable:: ist.recv_addr
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: value of :variable:`wsrep_node_address`
+
+This variable specifies the address on which nodes listens for Incremental State Transfer (|IST|).
+
+.. variable:: pc.checksum
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: true
+
+This variable controls will the replicated messages will be checksummed or not.
+
+.. variable::  pc.ignore_quorum
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: false
+
+When this variable is set to ``TRUE`` node will completely ignore the quorum calculations. This should be used with extreme caution even in master-slave setups, because slaves won't automatically reconnect to master in this case.
+
+.. variable::  pc.ignore_sb
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: false
+
+When this variable us set ti ``TRUE`` node will process updates even in the case of split brain. This should be used with extreme caution in multi-master setup, but should simplify things in master-slave cluster (especially if only 2 nodes are used).
+
+.. variable::  pc.linger 
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: PT20S
+
+This variable specifies the period which PC protocol waits for EVS termination.
+
+.. variable::  pc.npvo 
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: false
+
+When this variable is set to ``TRUE`` more recent primary component overrides older ones in case of conflicting prims.
+
+.. variable::  pc.version
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0
+
+.. variable::  pc.weight 
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: 1
+
+This variable specifies the node weight that's going to be used for Weighted Quorum calculations.
+
+.. variable::  protonet.backend
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: asio
+
+This variable is used to define which transport backend should be used. Currently only ``ASIO`` is supported.
+
+.. variable::  protonet.version
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 0
+
+.. variable::  repl.causal_read_timeout
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: PT30S
+
+This variable specifies the causal read timeout.
+
+.. variable::  repl.commit_order
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 3
+
+This variable is used to specify Out-Of-Order committing (which is used to improve parallel applying performance). Allowed values are:
+
+ * ``0`` – BYPASS: all commit order monitoring is turned off (useful for measuring performance penalty)
+ * ``1`` – OOOC: allow out of order committing for all transactions
+ * ``2`` – LOCAL_OOOC: allow out of order committing only for local transactions
+ * ``3`` – NO_OOOC: no out of order committing is allowed (strict total order committing)
+
+.. variable::  repl.key_format 
+ 
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :default: FLAT8
+
+This variable is used to specify the replication key format. Allowed values are:
+
+ * ``FLAT8`` shorter - higher probability of key match false positives
+ * ``FLAT16`` longer - lower probability of false positives. 
+ * ``FLAT8A`` - same as ``FLAT8`` but with annotations for debug purposes.
+ * ``FLAT16A`` - same as ``FLAT16`` but with annotations for debug purposes.
+
+.. variable::  repl.proto_max 
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 5
+
+This variable is used to specify the highest communication protocol version to accept in the cluster. This variable is used only for debugging.
+
+.. variable::  socket.checksum
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: 2
+
+This variable is used to choose the checksum algorithm for network packets. Available options are:
+
+ * ``0`` - disable checksum
+ * ``1`` - plain ``CRC32`` (used in Galera 2.x)
+ * ``2`` - hardware accelerated ``CRC32-C``
+
+.. variable::  socket.ssl
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: No
+
+This variable is used to specify if the SSL encryption should be used.
+
+
+.. variable::  socket.ssl_cert
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+
+This variable is used to specify the path (absolute or relative to working directory) to an SSL certificate (in PEM format).
+
+.. variable:: socket.ssl_key
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+
+
+This variable is used to specify the path (absolute or relative to working directory) to an SSL private key for the certificate (in PEM format).
+
+.. variable:: socket.ssl_compression
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: Yes
+
+This variable is used to specify if the SSL compression is to be used.
+
+.. variable:: socket.ssl_cipher	
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: No
+   :default: AES128-SHA 
+
+This variable is used to specify what cypher will be used for encryption.
+
+

=== modified file 'doc-pxc/source/wsrep-system-index.rst'
--- doc-pxc/source/wsrep-system-index.rst	2014-03-09 13:26:24 +0000
+++ doc-pxc/source/wsrep-system-index.rst	2014-03-20 09:44:42 +0000
@@ -327,7 +327,7 @@
    :dyn: Yes
    :default: 1
 
-This variable controls the number of threads that can apply replication transactions in parallel. Galera supports true parallel replication, replication that applies transactions in parallel only when it is safe to do so. The variable is dynamic, you can increase/decrease it anytime, note that, when you decrease it, it won't kill the threads immediately but stop them after they are done applying current transaction (the effect with increase is immediate though).  If any replication consistency problems are encountered, it's recommended to set this back to ``1`` to see if that resolves the issue. The default value can be increased for better throughput. You may want to increase it many a time as suggested `here <http://www.codership.com/wiki/doku.php?id=flow_control>`_, in JOINED state for instance to speed up the catchup process to SYNCED. You can also estimate the optimal value for this from :variable:`wsrep_cert_deps_distance` as suggested `here <http://www.codership.com/wiki/doku.php?id=monitoring#checking_replication_health>`_. You can also refer to `this <http://www.codership.com/wiki/doku.php?id=configuration_tips#parallel_applying_wsrep_slave_threads>`_ for more configuration tips.
+This variable controls the number of threads that can apply replication transactions in parallel. Galera supports true parallel replication, replication that applies transactions in parallel only when it is safe to do so. The variable is dynamic, you can increase/decrease it anytime, note that, when you decrease it, it won't kill the threads immediately but stop them after they are done applying current transaction (the effect with increase is immediate though).  If any replication consistency problems are encountered, it's recommended to set this back to ``1`` to see if that resolves the issue. The default value can be increased for better throughput. You may want to increase it many a time as suggested `in Codership documentation <http://www.codership.com/wiki/doku.php?id=flow_control>`_, in JOINED state for instance to speed up the catchup process to SYNCED. You can also estimate the optimal value for this from :variable:`wsrep_cert_deps_distance` as suggested `on this page <http://www.codership.com/wiki/doku.php?id=monitoring#checking_replication_health>`_. You can also refer to `this <http://www.codership.com/wiki/doku.php?id=configuration_tips#parallel_applying_wsrep_slave_threads>`_ for more configuration tips.
 
 .. variable:: wsrep_sst_auth