Merge lp:~hrvojem/percona-server/rn-5.6.16-64.0-tokudb-5.6 into lp:percona-server/5.6

[Hrvoje Matijakovic]

[Laurynas Biveinis (laurynas-biveinis)]

   - I am not sure why --rewrite-db is called a "variable". It's an
     option.
   - The TokuDB build version cannot be just "5.6.16-64.0", because
     it will conflict with the regular release having the same
     version. IIRC the TokuDB build scripts added something to the
     version string, so let's add the same thing here and use it
     uniformly.
   - TokuDB compression has to be documented with examples, listing
     of allowed row_type values, probably on its own page.
   - The TokuDB alpha features perhaps should be listed somewhere or
     users won't even know about their existence. Perhaps a short page
     for alpha features only which links to TokuDB pages on secondary
     clustering keys, prescans, NOAR, ONLINE OPTIMIZE, autoincrement
     would suffice.
   - 250: "have no differences and can be installed side by side if
     desired." It needs documenting what will happen on existing
     Percona-provided libmysqlclient package upgrade, and please run
     the resulting paragraph by BAlexey/raghu/tomislav for feedback.
   - 259: "due to a regression in the buffer pool mutex split, a
     combination of InnoDB compression, write workload, and multiple
     active purge threads could lead to a server crash".
   - 261: "Several fixes for multiple XA engine support in the server
     have been ported from MariaDB."
   - 265: "Fix for bug 1227581, a buffer pool mutex split regression,
     was not complete, thus a combination of write workload to InnoDB
     compressed table and a tablespace drop could crash the server".
   - 269: "The InnoDB page cleaner thread could have incorrectly
     decided whether the server is busy or idle on some of its
     iterations and consequently issue a too big flush list flushing
     request on a busy server, causing performance instabilities"
   - 273-275: join: "InnoDB did not handle the cases of asynchronous
     and synchronous I/O requests completing partially or being
     interrupted."
   - 277: "Fixed the upstream bug 70768: the fix for upstream bug
     70768 may cause a high rate of RW lock creations and
     desctructions, resulting in a performance regression on some
     workloads"
   - 279: "Debian and Ubuntu packaging has been reworked to meet the
     packaging standards"
   - 281: add 1274411 there too
   - 1277383 needs a RN entry
   - 1159625/1199534 may or may not need RN entries
   - 1204871 needs a RN entry
   - The multiple XA fixes need more details what was fixed in one
     bug and in the other.
   - 1229598 needs a RN entry
   - 1005787 needs a RN entry
   - 1264952 needs a RN entry
   - 1276445 and 1014477 might get a RN entry, "Percona Server source
     tree has been reorganized to match the MySQL source tree layout
     closer" "Permissions on some testsuite files have been
     corrected"
   - 1052636 needs a RN entry
   - 338: "availble"
   - 363-369: unify "INSTALL PLUGIN" case

review: Needs Fixing

[Laurynas Biveinis (laurynas-biveinis)]

    TokuDB review only
    - How is patching doc/source/conf.py to +release =
      '5.6.16-64.0-tokudb' is going to work for the next trunk
      releases?
    - 221,224: "-tokudb" to the version string
    - 250: only the 1st sentence enough
    - 309: s/that aren't available.../for TokuDB tables.
    - 311: s/bases/basis, uppercase ROW_FORMAT
    - 311: uppercase option names
    - 333: uppercase
    - 335: uppercase ROW_FORMAT
    - 343: "datayou'll"
    - How are the packages organized? Will yum install
      Percona-Server-tokudb-56.x86_64 / apt-get install
      percona-server-tokudb-5.6 install both the patched PS and the
      TokuDB SE as two packages, one joint package, or?
    - On alpha vs non-alpha features. (i.e. what's on the alpha tree,
      and what's on the trunk). The TokuDB compression is in the
      trunk, so it's not an alpha. The rest are not present in the
      trunk, thus I'll make a separate list for them and add a warning
      that these features might change or even disappear in a future
      release. I'd put these two lists both in the RNs and in
      tokudb_intro.rst.

review: Needs Fixing

[Laurynas Biveinis (laurynas-biveinis)]

    TokuDB review only
    - s/Features available only in ALPHA release/Currently available
      ALPHA features/g
    - footnotes: these features are available only in ALPHA Percona
      Server with TokuDB builds. They might change or ...
    - 266: s/algorithm names/algorithms
    - 329/332: uppercase option names
    - 337: uppercase
    - 349: uppercase
    - 355: uppercase

review: Needs Fixing

[Laurynas Biveinis (laurynas-biveinis)]

    TokuDB review only
    - 245, 490: "oreven"
    - 327: "with <missing> CPU utilization"

review: Needs Fixing

[Laurynas Biveinis (laurynas-biveinis)]

TokuDB review only

review: Approve

=== modified file '.bzrignore'
--- .bzrignore	2013-10-08 06:03:07 +0000
+++ .bzrignore	2014-03-03 18:33:47 +0000
@@ -3140,3 +3140,4 @@
 storage/perfschema/pfs_lex_token.h
 storage/perfschema/gen_pfs_lex_token
 sql/share/bulgarian
+doc/build

=== modified file 'doc/source/conf.py'
--- doc/source/conf.py	2014-03-03 17:51:33 +0000
+++ doc/source/conf.py	2014-03-03 18:33:47 +0000
@@ -45,7 +45,7 @@
 
 # General information about the project.
 project = u'Percona Server'
-copyright = u'Percona LLC and/or its affiliates 2009-2013'
+copyright = u'Percona LLC and/or its affiliates 2009-2014'
 
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
@@ -54,7 +54,7 @@
 # The short X.Y version.
 version = '5.6'
 # The full version, including alpha/beta/rc tags.
-release = '5.6.15-63.0'
+release = '5.6.16-64.0-tokudb'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
@@ -226,7 +226,7 @@
 # (source start file, target name, title, author, documentclass [howto/manual]).
 latex_documents = [
   ('index', 'PerconaServer-5.6.tex', u'Percona Server Documentation',
-   u'Percona LLC and/or its affiliates 2009-2013', 'manual'),
+   u'Percona LLC and/or its affiliates 2009-2014', 'manual'),
 ]
 
 # The name of an image file (relative to this directory) to place at the top of
@@ -259,7 +259,7 @@
 # (source start file, name, description, authors, manual section).
 man_pages = [
     ('index', 'perconaserver56', u'Percona Server 5.6 Documentation',
-     [u'Percona LLC and/or its affiliates 2009-2013'], 1)
+     [u'Percona LLC and/or its affiliates 2009-2014'], 1)
 ]
 
 

=== added file 'doc/source/flexibility/mysqlbinlog_change_db.rst'
--- doc/source/flexibility/mysqlbinlog_change_db.rst	1970-01-01 00:00:00 +0000
+++ doc/source/flexibility/mysqlbinlog_change_db.rst	2014-03-03 18:33:47 +0000
@@ -0,0 +1,89 @@
+.. _mysqlbinlog_change_db:
+
+==========================================
+Ability to change database for mysqlbinlog
+==========================================
+
+Sometimes there is a need to take a binary log and apply it to a database with 
+a different name than the original name of the database on binlog producer.
+
+New option rewrite-db has been added to the mysqlbinlog utility that allows the changing names of the used databases in both Row-Based and Statement-Based replication. This was possible before by using tools like grep, awk and sed but only for SBR, because with RBR database name is encoded within the BINLOG ‘....’ statement.
+
+Option :option:`rewrite-db` of **mysqlbinlog** utility allows to setup rewriting rule "from->"to".
+
+Example
+=======
+
+**mysqlbinlog** output before rewrite-db :: 
+
+ $ mysqlbinlog mysql-bin.000005
+ ...
+ # at 175
+ #120517 13:10:00 server id 2  end_log_pos 203   Intvar
+ SET INSERT_ID=4083/*!*/;
+ # at 203
+ #120517 13:10:00 server id 2  end_log_pos 367   Query   thread_id=88    exec_time=0     error_code=0
+ use world/*!*/;
+ SET TIMESTAMP=1337253000/*!*/;
+ insert into City (Name, CountryCode, District, Population) values ("New City", "ZMB", "TEX", 111000)
+ /*!*/;
+ # at 367
+ #120517 13:10:00 server id 2  end_log_pos 394   Xid = 1414
+ COMMIT/*!*/;
+ DELIMITER ;
+
+**mysqlbinlog** output when the new variable is used:  :: 
+
+ $ mysqlbinlog --rewrite-db='world->new_world' mysql-bin.000005
+ ...
+ # at 106
+ use new_world/*!*/;
+ #120517 13:10:00 server id 2  end_log_pos 175   Query   thread_id=88    exec_time=0     error_code=0
+ SET TIMESTAMP=1337253000/*!*/;
+ SET @@session.pseudo_thread_id=88/*!*/;
+ SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1, @@session.unique_checks=1, @@session.autocommit=1/*!*/;
+ SET @@session.sql_mode=0/*!*/;
+ SET @@session.auto_increment_increment=1, @@session.auto_increment_offset=1/*!*/;
+ /*!\C latin1 *//*!*/;
+ SET @@session.character_set_client=8,@@session.collation_connection=8,@@session.collation_server=8/*!*/;
+ SET @@session.lc_time_names=0/*!*/;
+ SET @@session.collation_database=DEFAULT/*!*/;
+ BEGIN
+ /*!*/;
+ # at 175
+ #120517 13:10:00 server id 2  end_log_pos 203   Intvar
+ SET INSERT_ID=4083/*!*/;
+ # at 203
+ #120517 13:10:00 server id 2  end_log_pos 367   Query   thread_id=88    exec_time=0     error_code=0
+ SET TIMESTAMP=1337253000/*!*/;
+ insert into City (Name, CountryCode, District, Population) values ("New City", "ZMB", "TEX", 111000)
+ /*!*/;
+ # at 367
+ #120517 13:10:00 server id 2  end_log_pos 394   Xid = 1414
+ COMMIT/*!*/;
+
+
+Version Specific Information
+============================
+
+  * :rn:`5.6.16-64.0`
+    Feature ported from |Percona Server| 5.1
+
+Client Command Line Parameter
+=============================
+
+.. option:: rewrite-db
+
+     :cli: Yes
+     :conf: Yes
+     :scope: Global
+     :dyn: No
+     :vartype: String
+     :default: Off
+
+
+Related Reading
+===============
+
+  * `WL #36 <http://askmonty.org/worklog/Server-Sprint/?tid=36>`_
+

=== modified file 'doc/source/index.rst'
--- doc/source/index.rst	2014-03-03 17:51:33 +0000
+++ doc/source/index.rst	2014-03-03 18:33:47 +0000
@@ -89,6 +89,7 @@
    flexibility/extended_select_into_outfile
    flexibility/per_query_variable_statement
    flexibility/extended_mysqlbinlog
+   flexibility/mysqlbinlog_change_db
 
 Reliability Improvements
 ========================
@@ -140,6 +141,18 @@
    diagnostics/misc_info_schema_tables
    diagnostics/thread_based_profiling
 
+TokuDB
+======
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   tokudb/tokudb_intro
+   tokudb/tokudb_installation
+   tokudb/using_tokudb
+   tokudb/tokudb_compression
+
 Reference
 =========
 

=== modified file 'doc/source/installation/apt_repo.rst'
--- doc/source/installation/apt_repo.rst	2013-12-19 13:40:34 +0000
+++ doc/source/installation/apt_repo.rst	2014-03-03 18:33:47 +0000
@@ -42,14 +42,13 @@
  * 13.10 (saucy)
 
 
-Release Candidate Repository
-============================
-
-To subscribe to the release candidate repository, add two lines to the :file:`/etc/apt/sources.list` file, again replacing ``VERSION`` with your server's release version: ::
-
-  deb http://repo.percona.com/apt-rc VERSION main
-  deb-src http://repo.percona.com/apt-rc VERSION main
-
+Percona `apt` Experimental repository
+=====================================
+
+Percona offers fresh beta builds from the experimental repository. To enable it add the following lines to your  :file:`/etc/apt/sources.list` , replacing ``VERSION`` with the name of your distribution: :: 
+
+  deb http://repo.percona.com/apt VERSION main experimental
+  deb-src http://repo.percona.com/apt VERSION main experimental
 
 Apt-Pinning the packages
 ========================

=== modified file 'doc/source/ps-versions-comparison.rst'
--- doc/source/ps-versions-comparison.rst	2013-12-19 13:40:34 +0000
+++ doc/source/ps-versions-comparison.rst	2014-03-03 18:33:47 +0000
@@ -45,7 +45,7 @@
      - Replaced by the upstream implementation [#n-4]_
    * - :ref:`Reduced Buffer Pool Mutex Contention <ps51:innodb_opt_lru_count>`
      - :ref:`Reduced Buffer Pool Mutex Contention <ps55:innodb_opt_lru_count>`
-     - :ref:`Reduced Buffer Pool Mutex Contention <ps56:innodb_opt_lru_count>`
+     - Feature not implemented 
    * - :ref:`InnoDB timer-based Concurrency Throttling <ps51:innodb_thread_concurrency_timer_based_page>`
      - :ref:`InnoDB timer-based Concurrency Throttling <ps55:innodb_thread_concurrency_timer_based_page>`
      - Replaced by the upstream implementation [#n-5]_

=== added file 'doc/source/release-notes/Percona-Server-5.6.16-64.0-tokudb.rst'
--- doc/source/release-notes/Percona-Server-5.6.16-64.0-tokudb.rst	1970-01-01 00:00:00 +0000
+++ doc/source/release-notes/Percona-Server-5.6.16-64.0-tokudb.rst	2014-03-03 18:33:47 +0000
@@ -0,0 +1,28 @@
+.. rn:: 5.6.16-64.0-tokudb
+
+========================================================
+ |Percona Server| 5.6.16-64.0-tokudb with TokuDB engine
+========================================================
+
+Percona is glad to announce the first **ALPHA** release of |Percona Server| 5.6.16-64.0-tokudb with TokuDB engine on March 3rd, 2014. Downloads are available `here <http://www.percona.com/downloads/TESTING/Percona-5.6-TokuDB/545/>`_ and from the :ref:`Percona Software Repositories <tokudb_installation>`.
+
+Based on |Percona Server| :rn:`5.6.16-64.0` including all the features and bug fixes in it, and on TokuDB 7.1.5-rc.3, |Percona Server| 5.6.16-64.0-tokudb is the first **ALPHA** release in the |Percona Server| 5.6 with TokuDB series. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.6.16-64.0 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.6.16-64.0>`_.
+
+New Features
+============
+
+|Percona Server| now supports TokuDB storage engine. More information on how to :ref:`install <tokudb_installation>` and :ref:`use <using_tokudb>` TokuDB can be found in the documentation. This feature is currently considered ALPHA quality.
+
+Available TokuDB features:
+
+ * :ref:`tokudb_compression`
+
+Currently available ALPHA features [#n-1]_:
+
+ * `Multiple Clustering Indexes <http://www.tokutek.com/2009/05/introducing_multiple_clustering_indexes/>`_
+ * `Fast Updates with NOAR <http://www.tokutek.com/2013/02/fast-updates-with-tokudb/>`_
+ * `Hot Table Optimization <http://www.tokutek.com/2012/06/hot-table-optimization-with-mysql/>`_
+ * `TokuDB AUTOINCREMENT implementation <http://www.tokutek.com/2009/07/autoincrement_semantics/>`_
+ * `Prelocking index and range scans <https://github.com/Tokutek/mysql56/wiki/Patch-for-prelocking-index-and-range-scans>`_
+
+.. [#n-1] These features are available only in ALPHA Percona Server with TokuDB builds. They might change or even disappear in a future release.

=== added file 'doc/source/release-notes/Percona-Server-5.6.16-64.0.rst'
--- doc/source/release-notes/Percona-Server-5.6.16-64.0.rst	1970-01-01 00:00:00 +0000
+++ doc/source/release-notes/Percona-Server-5.6.16-64.0.rst	2014-03-03 18:33:47 +0000
@@ -0,0 +1,47 @@
+.. rn:: 5.6.16-64.0
+
+=================================================
+ |Percona Server| 5.6.16-64.0 [Not Released Yet]
+=================================================
+
+Percona is glad to announce the release of |Percona Server| 5.6.16-64.0 on March 6th, 2014 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.16-64.0/>`_ and from the :doc:`Percona Software Repositories </installation>`).
+
+Based on `MySQL 5.6.16 <http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-16.html>`_, including all the bug fixes in it, |Percona Server| 5.6.16-64.0 is the current GA release in the |Percona Server| 5.6 series. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.6.16-64.0 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.6.16-64.0>`_.
+
+New Features
+============
+
+ |Percona Server| now supports :ref:`tokudb_compression` algorithms.
+
+ In order to comply with Linux distribution packaging standards |Percona|'s version of ``libmysqlclient`` has been renamed to ``libperconaserver``. The reason this was done was to avoid name conflicts with packages upstream name and library conflicts, otherwise, ``libmysqlclient`` and ``libperconaserverclient`` of same version have no differences. Users will have to use ``libmysqlclient`` of respective distributions, for *CentOS* it is ``mysql-libs`` and for *Ubuntu*/*Debian* it is ``libmysqlclient18`` package. 
+ 
+ :ref:`mysqlbinlog_change_db` has been ported from |Percona Server| 5.1.
+
+Bugs Fixed
+==========
+
+ |Percona Server| 5.6 installation on *Debian* would fail due to default config reference to ``/etc/mysql/conf.d`` which didn't exist. Bug fixed :bug:`1206648`.
+
+ Due to a regression in the buffer pool mutex split, a combination of |InnoDB| compression, write workload, and multiple active purge threads could lead to a server crash. Bug fixed :bug:`1247021`.
+
+ Several fixes for multiple XA engine support in the server have been ported from |MariaDB|. Bugs fixed :bug:`1255551` (upstream :mysqlbug:`70854`) and :bug:`1255549` (upstream :mysqlbug:`47134`).
+ 
+ ``auth_pam.so`` shared library needed for :ref:`pam_plugin` was missing from ``RPM`` packages. Bug fixed :bug:`1268246`.
+
+ Fix for bug :bug:`1227581`, a buffer pool mutex split regression, was not complete, thus a combination of write workload to |InnoDB| compressed table and a tablespace drop could crash the server. Bug fixed :bug:`1269352`.
+
+ |Percona Server| compilation with Performance Schema turned off would fail due to regression introduced by the 5.6 priority mutex framework. Bug fixed :bug:`1272747`.
+
+ The |InnoDB| page cleaner thread could have incorrectly decided whether the server is busy or idle on some of its iterations and consequently issue a too big flush list flushing request on a busy server, causing performance instabilities. Bug fixed :bug:`1238039`.
+
+ |Percona Server| had different server version value when installing from Source and from Binary/RPM. Bug fixed :bug:`1244178`.
+ 
+ |InnoDB| did not handle the cases of asynchronous and synchronous I/O requests completing partially or being interrupted. Bugs fixed :bug:`1262500` (upstream :mysqlbug:`54430`), and :bug:`1263087` (*Andrew Gaul*).
+
+ Fixed the upstream bug :mysqlbug:`70768`: the fix for upstream bug :mysqlbug:`70768` may cause a high rate of RW lock creations and desctructions, resulting in a performance regression on some workloads. Bug fixed :bug:`1279671`.
+
+ *Debian* and *Ubuntu* packaging has been reworked to meet the packaging standards. Bug fixed :bug:`1281261`.
+
+ Fixed the ``CMake`` warnings that were happening when ``Makefile`` was generated. Bugs fixed :bug:`1274827`, upstream bug fixed :mysqlbug:`71089` and :bug:`1274411` (upstream :mysqlbug:`71094`).
+
+Other bugs fixed: :bug:`1052636`, :bug:`1014477`, :bug:`1276445`, :bug:`1274827` (upstream :mysqlbug:`71089`), :bug:`1264952`, :bug:`1005787`, :bug:`1285064`, :bug:`1229598`, :bug:`1277505` (upstream :mysqlbug:`71624`), and :bug:`1204871` (upstream :mysqlbug:`71270`).

=== modified file 'doc/source/release-notes/release-notes_index.rst'
--- doc/source/release-notes/release-notes_index.rst	2014-03-03 17:51:33 +0000
+++ doc/source/release-notes/release-notes_index.rst	2014-03-03 18:33:47 +0000
@@ -6,6 +6,8 @@
    :maxdepth: 1
    :glob:
 
+   Percona-Server-5.6.16-64.0-tokudb
+   Percona-Server-5.6.16-64.0
    Percona-Server-5.6.15-63.0
    Percona-Server-5.6.14-62.0
    Percona-Server-5.6.13-61.0

=== added directory 'doc/source/tokudb'
=== added file 'doc/source/tokudb/tokudb_compression.rst'
--- doc/source/tokudb/tokudb_compression.rst	1970-01-01 00:00:00 +0000
+++ doc/source/tokudb/tokudb_compression.rst	2014-03-03 18:33:47 +0000
@@ -0,0 +1,45 @@
+.. _tokudb_compression:
+
+====================
+ TokuDB Compression
+====================
+
+TokuDB storage engine provides new compression options for TokuDB tables.
+
+These options are defined on per-table basis by setting ``ROW_FORMAT`` during a ``CREATE TABLE`` or ``ALTER TABLE``. If no value is specified for ``ROW_FORMAT`` ``zlib`` compression is used by default. Currently available formats are:
+
+ * ``TOKUDB_ZLIB`` - This compression is using ``zlib`` library and provides mid-range compression with medium CPU utilization.
+ * ``TOKUDB_QUICKLZ`` - This compression is using ``quicklz`` library and provides light compression with low CPU utilization.
+ * ``TOKUDB_LZMA`` - This compression is using ``lzma`` library and provides the highest compression with high CPU utilization.
+ * ``TOKUDB_UNCOMPRESSED`` - This option disables the compression.
+
+Example
+-------
+
+In order to create a new table with the highest compression you need to specify the ``TOKUDB_LZMA`` as the ``ROW_FORMAT``: 
+
+.. code-block:: mysql
+
+ mysql> CREATE TABLE `City` (
+   > `ID` int(11) NOT NULL AUTO_INCREMENT,
+     `Name` char(35) NOT NULL DEFAULT '',
+     `CountryCode` char(3) NOT NULL DEFAULT '',
+     `District` char(20) NOT NULL DEFAULT '',
+     `Population` int(11) NOT NULL DEFAULT '0',
+     PRIMARY KEY (`ID`),
+     KEY `CountryCode` (`CountryCode`)
+   ) ENGINE=TokuDB, ROW_FORMAT=TOKUDB_LZMA;
+
+In order to change the compression for this table you need to change the ``ROW_FORMAT`` with ``ALTER TABLE`` command:
+
+.. code-block:: mysql
+
+ mysql> ALTER TABLE City ROW_FORMAT=TOKUDB_ZLIB;
+
+.. note:: 
+
+  When the compression format is changed it will affect only newly written data. In order to change the old data you'll need to run ``OPTIMIZE TABLE`` on that table.
+
+  .. code-block:: mysql
+
+    mysql> OPTIMIZE TABLE City;

=== added file 'doc/source/tokudb/tokudb_installation.rst'
--- doc/source/tokudb/tokudb_installation.rst	1970-01-01 00:00:00 +0000
+++ doc/source/tokudb/tokudb_installation.rst	2014-03-03 18:33:47 +0000
@@ -0,0 +1,96 @@
+.. _tokudb_installation:
+
+=====================
+ TokuDB Installation
+=====================
+
+.. warning:: 
+
+   This feature is considered **ALPHA** quality and it isn't recommended for production use.
+
+|Percona Server| has added support for TokuDB storage engine in the :rn:`5.6.16-64.0-tokudb` release. 
+
+`TokuDB <http://www.tokutek.com/products/tokudb-for-mysql/>`_ is a scalable, ACID and MVCC compliant storage engine that provides indexing-based query improvements, offers online schema modifications, and reduces slave lag for both hard disk drives and flash memory. This storage engine is specifically designed for high performance on write-intensive workloads which is achieved with Fractal Tree indexing.
+
+TokuDB is currently supported only for 64-bit Linux distributions.
+
+Installation
+============
+
+|Percona Server| with TokuDB is currently available in our :ref:`apt experimental <apt_repo>` and :ref:`yum testing <yum_repo>` repositories. 
+
+You can install the |Percona Server| with TokuDB engine by using the apt/yum commands:
+
+.. code-block:: bash
+
+ [root@centos ~]# yum install Percona-Server-tokudb-56.x86_64
+
+or 
+
+.. code-block:: bash
+
+ root@wheezy:~# apt-get install percona-server-tokudb-5.6
+
+.. note::
+
+ TokuDB won't be able to start if the transparent huge pages are enabled. `Transparent huge pages <https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Performance_Tuning_Guide/s-memory-transhuge.html>`_ is feature available in the newer kernel versions. You can check if the Transparent huge pages are enabled with: ::
+  
+   $ cat /sys/kernel/mm/transparent_hugepage/enabled
+
+   [always] madvise never
+
+ You can `disable <http://www.oracle-base.com/articles/linux/configuring-huge-pages-for-oracle-on-linux-64.php#disabling-transparent-hugepages>`_ them by passing ``transparent_hugepage=never`` to the kernel in your bootloader or by running: :: 
+
+  $ echo never > /sys/kernel/mm/transparent_hugepage/enabled
+  $ echo never > /sys/kernel/mm/transparent_hugepage/defrag
+
+
+Upgrade
+=======
+
+Upgrading from other |Percona Server| 5.5 and 5.6 releases should work without problems (you should read :ref:`changed_in_56` before upgrading from |Percona Server| 5.5 to |Percona Server| 5.6 with TokuDB engine). 
+
+
+Enabling the TokuDB support
+===========================
+
+This plugin requires manual installation because it isn't installed by default.
+
+.. code-block:: mysql
+
+ mysql> INSTALL PLUGIN tokudb SONAME 'ha_tokudb.so';
+ mysql> INSTALL PLUGIN tokudb_file_map SONAME 'ha_tokudb.so';
+ mysql> INSTALL PLUGIN tokudb_fractal_tree_info SONAME 'ha_tokudb.so';
+ mysql> INSTALL PLUGIN tokudb_fractal_tree_block_map SONAME 'ha_tokudb.so';
+ mysql> INSTALL PLUGIN tokudb_trx SONAME 'ha_tokudb.so';
+ mysql> INSTALL PLUGIN tokudb_locks SONAME 'ha_tokudb.so';
+ mysql> INSTALL PLUGIN tokudb_lock_waits SONAME 'ha_tokudb.so';
+
+After the engine has been installed it should be present in the engines list. To check if the engine has been correctly installed and active: 
+
+.. code-block:: mysql
+
+ mysql> SHOW ENGINES;
+ ...
+ | TokuDB | YES | Tokutek TokuDB Storage Engine with Fractal Tree(tm) Technology | YES | YES | YES |
+ ...
+
+To check if all the TokuDB plugins have been installed correctly you should run:
+
+.. code-block:: mysql
+
+ mysql> SHOW PLUGINS;
+ ...
+ | TokuDB                        | ACTIVE   | STORAGE ENGINE     | ha_tokudb.so | GPL     |
+ | TokuDB_file_map               | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
+ | TokuDB_fractal_tree_info      | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
+ | TokuDB_fractal_tree_block_map | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
+ | TokuDB_trx                    | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
+ | TokuDB_locks                  | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
+ | TokuDB_lock_waits             | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
+ ...
+
+Other Reading
+=============
+
+* `Official TokuDB Documentation <http://www.tokutek.com/resources/product-docs/>`_

=== added file 'doc/source/tokudb/tokudb_intro.rst'
--- doc/source/tokudb/tokudb_intro.rst	1970-01-01 00:00:00 +0000
+++ doc/source/tokudb/tokudb_intro.rst	2014-03-03 18:33:47 +0000
@@ -0,0 +1,23 @@
+.. _tokudb_intro:
+
+=====================
+ TokuDB Introduction
+=====================
+
+TokuDB is a scalable, ACID and MVCC compliant storage engine that provides indexing-based query improvements, offers online schema modifications, and reduces slave lag for both hard disk drives and flash memory. This storage engine is specifically designed for high performance on write-intensive workloads which is achieved with Fractal Tree indexing.
+
+Available TokuDB features:
+
+ * :ref:`tokudb_compression`
+
+Currently available ALPHA features [#n-1]_:
+
+ * `Multiple Clustering Indexes <http://www.tokutek.com/2009/05/introducing_multiple_clustering_indexes/>`_
+ * `Fast Updates with NOAR <http://www.tokutek.com/2013/02/fast-updates-with-tokudb/>`_
+ * `Hot Table Optimization <http://www.tokutek.com/2012/06/hot-table-optimization-with-mysql/>`_
+ * `TokuDB AUTOINCREMENT implementation <http://www.tokutek.com/2009/07/autoincrement_semantics/>`_
+ * `Prelocking index and range scans <https://github.com/Tokutek/mysql56/wiki/Patch-for-prelocking-index-and-range-scans>`_
+
+.. rubric:: Footnotes
+
+.. [#n-1] These features are available only in ALPHA Percona Server with TokuDB builds. They might change or even disappear in a future release.

=== added file 'doc/source/tokudb/using_tokudb.rst'
--- doc/source/tokudb/using_tokudb.rst	1970-01-01 00:00:00 +0000
+++ doc/source/tokudb/using_tokudb.rst	2014-03-03 18:33:47 +0000
@@ -0,0 +1,33 @@
+.. _using_tokudb:
+
+==============
+ Using TokuDB
+==============
+
+TokuDB storage engine can be used as the rest of the already available |MySQL| engines. You can create the TokuDB tables by specifying TokuDB when creating the tables:
+
+.. code-block:: mysql
+
+   mysql> CREATE TABLE `City` (
+    `ID` int(11) NOT NULL AUTO_INCREMENT,
+    `Name` char(35) NOT NULL DEFAULT '',
+    `CountryCode` char(3) NOT NULL DEFAULT '',
+    `District` char(20) NOT NULL DEFAULT '',
+    `Population` int(11) NOT NULL DEFAULT '0',
+    PRIMARY KEY (`ID`),
+    KEY `CountryCode` (`CountryCode`) 
+   ) ENGINE=TokuDB
+
+You can also convert existing tables to TokuDB by running ``ALTER TABLE``:
+
+.. code-block:: mysql
+
+   mysql> ALTER TABLE City ENGINE=TokuDB;
+
+Other Reading
+=============
+
+* `InnoDB vs TokuDB comparison <http://www.tokutek.com/resources/tokudb-vs-innodb/>`_
+* `TokuDB vs InnoDB in timeseries INSERT benchmark <http://www.mysqlperformanceblog.com/2013/09/05/tokudb-vs-innodb-timeseries-insert-benchmark/>`_
+* `Considering TokuDB as an engine for timeseries data <http://www.mysqlperformanceblog.com/2013/08/29/considering-tokudb-as-an-engine-for-timeseries-data/>`_
+* `Benchmarking Percona Server TokuDB vs InnoDB <http://www.mysqlperformanceblog.com/2013/05/07/benchmarking-percona-server-tokudb-vs-innodb/>`_