<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://www.codership.com/wiki/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://www.codership.com/wiki/feed.php">
        <title>Galera Replication</title>
        <description></description>
        <link>http://www.codership.com/wiki/</link>
        <image rdf:resource="http://www.codership.com/wiki/lib/tpl/vector/images/favicon.ico" />
       <dc:date>2012-05-18T04:11:38+03:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=certification&amp;rev=1303672679&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=cluster_control_galera_ec2&amp;rev=1323571736&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=compile_galera&amp;rev=1333031084&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=configuration_tips&amp;rev=1325120957&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=faq&amp;rev=1329421658&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=flow_control&amp;rev=1307469396&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_arbitrator&amp;rev=1315063549&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_deployment&amp;rev=1314445515&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_node_fsm&amp;rev=1307109865&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_parameters&amp;rev=1325121329&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_parameters_0.7&amp;rev=1301601912&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_parameters_0.8&amp;rev=1317255872&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_status_0.7&amp;rev=1301604062&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_status_0.8&amp;rev=1307497202&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_url&amp;rev=1301529713&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=galera_wiki&amp;rev=1312489805&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=gcache&amp;rev=1317731023&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=herethefirst_title&amp;rev=1332073773&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=howto&amp;rev=1333030012&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=info&amp;rev=1327086451&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=ist&amp;rev=1332073773&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=limitations&amp;rev=1311811061&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=manual&amp;rev=1330554379&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=monitoring&amp;rev=1332073773&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=mysql_galera_cluster_upgrade&amp;rev=1312576851&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=mysql_galera_howto&amp;rev=1332073773&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=mysql_options_0.7&amp;rev=1301530729&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=mysql_options_0.8&amp;rev=1323574117&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=node_failure&amp;rev=1307472175&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=node_provisioning_recovery&amp;rev=1307109450&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=notification_command&amp;rev=1333621452&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=reference&amp;rev=1332549102&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=rolling_schema_upgrade&amp;rev=1323574668&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=scriptable_state_snapshot_transfer&amp;rev=1325122566&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=ssl_support&amp;rev=1314391493&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=start&amp;rev=1297308785&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=state_transfer_protocol&amp;rev=1332073773&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=title_for_a_wiki_post&amp;rev=1332073773&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.codership.com/wiki/doku.php?id=wiki_editing_title&amp;rev=1332073773&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://www.codership.com/wiki/lib/tpl/vector/images/favicon.ico">
        <title>Galera Replication</title>
        <link>http://www.codership.com/wiki/</link>
        <url>http://www.codership.com/wiki/lib/tpl/vector/images/favicon.ico</url>
    </image>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=certification&amp;rev=1303672679&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-04-24T22:17:59+03:00</dc:date>
        <title>certification</title>
        <link>http://www.codership.com/wiki/doku.php?id=certification&amp;rev=1303672679&amp;do=diff</link>
        <description>How multi-master Galera replication works.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=cluster_control_galera_ec2&amp;rev=1323571736&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-11T04:48:56+03:00</dc:date>
        <title>cluster_control_galera_ec2</title>
        <link>http://www.codership.com/wiki/doku.php?id=cluster_control_galera_ec2&amp;rev=1323571736&amp;do=diff</link>
        <description>Severalnines team has added Galera cluster support to its ClusterControl(tm) configurator. Now it has become even easier and faster to deploy a 10-node Galera cluster anywhere from your private LAN to Amazon EC2. Plus it allows to conveniently monitor the cluster and individual nodes using nothing but a web browser. This page explains how to use ClusterControl to install and monitor Galera cluster in EC2.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=compile_galera&amp;rev=1333031084&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-29T17:24:44+03:00</dc:date>
        <title>compile_galera</title>
        <link>http://www.codership.com/wiki/doku.php?id=compile_galera&amp;rev=1333031084&amp;do=diff</link>
        <description>Linux

Coming later. Nothing special there. Check Solaris section for tips.

RHEL/CentOS/Oracle Linux

Debian

Solaris

Currently the latest revision of Galera is known to compile on Solaris 11 x86 in addition to Linux. It may not compile on Solaris 10, and will not work on big-endian machines (as we don't have any, we simply can't fix all the endian-related stuff).</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=configuration_tips&amp;rev=1325120957&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-29T03:09:17+03:00</dc:date>
        <title>configuration_tips</title>
        <link>http://www.codership.com/wiki/doku.php?id=configuration_tips&amp;rev=1325120957&amp;do=diff</link>
        <description>Parallel Applying (wsrep_slave_threads)

There is no rigorous rule about how many slave threads one should configure as well as having parallel threads won't guarantee better performance -- a lot depends on the application and use case. However parallel applying won't hurt regular operation performance and most likely will drastically speed up syncing new nodes with the cluster.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=faq&amp;rev=1329421658&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-02-16T21:47:38+03:00</dc:date>
        <title>faq</title>
        <link>http://www.codership.com/wiki/doku.php?id=faq&amp;rev=1329421658&amp;do=diff</link>
        <description>Q: What is Galera?

Galera is a wsrep service provider in a form of dlopenable library. It provides synchronous replication guarantees and supports multi-master replication. Among other things Galera is capable of unconstrained parallel applying AKA “parallel replication”, multicast replication and automatic node provisioning. Galera primary focus is data consistency: transaction is either applied on every node or not at all. See CaP theorem for consequences.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=flow_control&amp;rev=1307469396&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-07T20:56:36+03:00</dc:date>
        <title>flow_control</title>
        <link>http://www.codership.com/wiki/doku.php?id=flow_control&amp;rev=1307469396&amp;do=diff</link>
        <description>To ensure temporal synchrony and consistency (as opposed to logical which is provided by virtual synchrony), Galera implements several forms of low control depending on the node state:

writeset cacheslave queue

OPEN &amp; PRIMARY

The node is not considered to be a part of the cluster, it is not allowed to replicate, apply or cache any writesets. No flow control.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_arbitrator&amp;rev=1315063549&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-09-03T18:25:49+03:00</dc:date>
        <title>galera_arbitrator</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_arbitrator&amp;rev=1315063549&amp;do=diff</link>
        <description>Starting with version 0.8.2 Galera comes with an “arbitrator” garbd, a stateless daemon which acts as a lightweight group member and can serve two purposes:

	*  Help to avoid split-brain situation by acting as an odd node
	*  Request a consistent application state snapshot</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_deployment&amp;rev=1314445515&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-27T14:45:15+03:00</dc:date>
        <title>galera_deployment</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_deployment&amp;rev=1314445515&amp;do=diff</link>
        <description>Due to its synchronous multi-master qualities Galera cluster can be thought of simply as a single server listening at many interfaces. This however does not suggest any of the many possible Galera deployment variants. Just to give an idea of what is possible we'll consider a typical N-tier application and discuss different ways, benefits and drawbacks of deploying Galera cluster there.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_node_fsm&amp;rev=1307109865&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-03T17:04:25+03:00</dc:date>
        <title>galera_node_fsm</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_node_fsm&amp;rev=1307109865&amp;do=diff</link>
        <description>Different Galera layers have different state machines, depending on their semantics. The top layer that represents “node” state has the following FSM:

Regular Transitions:

[Galera Node FSM]

	*  Node establishes connection to a primary component.
	*  Node succeeds in state transfer request. It starts to cache the writesets.
	*  Node receives state snapshot. Now it has all cluster data and can start applying the cached writesets. Flow control is turned on to ensure eventual slave queue decrease…</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_parameters&amp;rev=1325121329&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-29T03:15:29+03:00</dc:date>
        <title>galera_parameters</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_parameters&amp;rev=1325121329&amp;do=diff</link>
        <description>Galera Parameters

As of 0.8 Galera accepts parameters in the form of semicolon-separated key=value pair list: “key1 = value1; key2 = value2” (in addition to Galera URL). It can be used to configure arbitrary number of Galera parameters in one call. A key consists of parameter group and parameter name: &lt;group&gt;.&lt;name&gt;, where group roughly corresponds to some Galera module.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_parameters_0.7&amp;rev=1301601912&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-31T23:05:12+03:00</dc:date>
        <title>galera_parameters_0.7</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_parameters_0.7&amp;rev=1301601912&amp;do=diff</link>
        <description>Galera 0.7.x parameters

Galera group communication backend properties can be customized through the option list in the cluster address URL.

Time periods must be expressed in ISO8601 format. Also see examples below.
 Parameter                     Default Description evs.consensus_timeout      PT30S   Timeout on reaching the consensus about cluster membership. evs.debug_log_mask         0x1     Control EVS debug logging, only effective when wsrep_debug is turned on. evs.inactive_check_period  PT…</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_parameters_0.8&amp;rev=1317255872&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-09-29T03:24:32+03:00</dc:date>
        <title>galera_parameters_0.8</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_parameters_0.8&amp;rev=1317255872&amp;do=diff</link>
        <description>Galera 0.8.x parameters

As of 0.8 Galera accepts parameters in the form of semicolon-separated key=value pair list: “key1 = value1; key2 = value2” (in addition to Galera URL). It can be used to configure arbitrary number of Galera parameters in one call.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_status_0.7&amp;rev=1301604062&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-31T23:41:02+03:00</dc:date>
        <title>galera_status_0.7</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_status_0.7&amp;rev=1301604062&amp;do=diff</link>
        <description>Status Variable                   Example Value                         Description  wsrep_local_state_uuid      G  e2c9a15e-5485-11e0-0800-6bbb637e7211  UUID of the state stored on this node.  wsrep_last_committed        G  409745                                Sequence number of the last committed transaction.  wsrep_replicated            G  16109                                 Total number of writesets replicated (sent to other nodes).  wsrep_replicated_bytes      G  6526788                 …</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_status_0.8&amp;rev=1307497202&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-08T04:40:02+03:00</dc:date>
        <title>galera_status_0.8</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_status_0.8&amp;rev=1307497202&amp;do=diff</link>
        <description>There two types of wsrep-related status variables: those exported by Galera (and therefore Galera-specific) and those exported by MySQL, which are of general wsrep provider purpose. This distinction is of importance only from the developer point of view, and therefor for convenience all those status variables are presented as a single list:</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_url&amp;rev=1301529713&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-31T03:01:53+03:00</dc:date>
        <title>galera_url</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_url&amp;rev=1301529713&amp;do=diff</link>
        <description>For the cluster address (where to connect to cluster at) Galera takes URL in the form
&lt;backend schema&gt;://&lt;cluster address&gt;[?option1=value1[&amp;option2=value2]]
which can be optionally followed by a list of key=value queries according to URL standard. In 0.7 it is the only way to customized Galera parameters. In 0.8 values supplied in the URL take precedence over the values supplied in wsrep_provider_options variable.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=galera_wiki&amp;rev=1312489805&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-04T23:30:05+03:00</dc:date>
        <title>galera_wiki</title>
        <link>http://www.codership.com/wiki/doku.php?id=galera_wiki&amp;rev=1312489805&amp;do=diff</link>
        <description>General Information

Reference

FAQ

HOWTO</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=gcache&amp;rev=1317731023&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-04T15:23:43+03:00</dc:date>
        <title>gcache</title>
        <link>http://www.codership.com/wiki/doku.php?id=gcache&amp;rev=1317731023&amp;do=diff</link>
        <description>Starting with version 1.0 Galera stores writesets in a special cache. It's purpose is to improve control of Galera memory usage and offload writeset storage to disk (see also this faq). Galera cache has 3 types of stores:

	*  A permanent in-memory store, where writesets are allocated by a default OS memory allocator. It can be useful for systems with spare RAM. It has a hard size limit. By default it is disabled (size set to 0).
	*  A permanent ring-buffer file which is preallocated on disk dur…</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=herethefirst_title&amp;rev=1332073773&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-18T14:29:33+03:00</dc:date>
        <title>herethefirst_title</title>
        <link>http://www.codership.com/wiki/doku.php?id=herethefirst_title&amp;rev=1332073773&amp;do=diff</link>
        <description>Hi to all on this page its content</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=howto&amp;rev=1333030012&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-29T17:06:52+03:00</dc:date>
        <title>howto</title>
        <link>http://www.codership.com/wiki/doku.php?id=howto&amp;rev=1333030012&amp;do=diff</link>
        <description>*  Galera cluster deployment variants
	*  MySQL/Galera cluster upgrade
	*  Use ClusterControl(tm) to deploy Galera cluster in Amazon EC2 in less than 10 minutes
	*  Compile Galera from source

External resources

	*  Fromdual: Migrating from MySQL replication to Galera cluster
	*  Fromdual: Rolling upgrade from Galera-1.0/MySQL-5.1 to Galera-1.1/MySQL-5.5</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=info&amp;rev=1327086451&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-20T21:07:31+03:00</dc:date>
        <title>info</title>
        <link>http://www.codership.com/wiki/doku.php?id=info&amp;rev=1327086451&amp;do=diff</link>
        <description>What we'll be talking here is a generic pluggable replication architecture of the form:


        clients
        |  |  |
        V  V  V
  ,----------------.
  |                |
  |   application  | &lt;-- e.g. MySQL server
  |                |
  ================== &lt;-- wsrep API
  | wsrep provider | &lt;-- e.g. Galera
  `----------------'
           |
           V
replication to other nodes</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=ist&amp;rev=1332073773&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-18T14:29:33+03:00</dc:date>
        <title>ist</title>
        <link>http://www.codership.com/wiki/doku.php?id=ist&amp;rev=1332073773&amp;do=diff</link>
        <description>Galera 2.x introduces a long awaited functionality: incremental state transfer.
It means that if

	*  the joining node state UUID is the same as that of the group and
	*  all of the writesets that it missed can be found in the donor's Gcache

then instead of whole state snapshot it will receive the missing writesets and catch up with the group by replaying them.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=limitations&amp;rev=1311811061&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-28T02:57:41+03:00</dc:date>
        <title>limitations</title>
        <link>http://www.codership.com/wiki/doku.php?id=limitations&amp;rev=1311811061&amp;do=diff</link>
        <description>This page lists limitations of MySQL/Galera replication.

	*  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... or GRANT... but issuing: INSERT INTO mysql.user... will not be replicated. In general, non-transactional engines cannot be supp…</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=manual&amp;rev=1330554379&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-01T00:26:19+03:00</dc:date>
        <title>manual</title>
        <link>http://www.codership.com/wiki/doku.php?id=manual&amp;rev=1330554379&amp;do=diff</link>
        <description>A Little Bit Of Theory

We strongly advise you to take time to familiarize yourself with the theory behind Galera operation. It is not that big or complex, however it will help you to understand Galera versatility and take you much farther than a thousand of examples or recipes. Galera takes data replication to a whole new level and to achieve that it does away with many “traditional” concepts and misconceptions. Whether you're a fledging DBA or a seasoned systems integrator with tens of “tradit…</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=monitoring&amp;rev=1332073773&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-18T14:29:33+03:00</dc:date>
        <title>monitoring</title>
        <link>http://www.codership.com/wiki/doku.php?id=monitoring&amp;rev=1332073773&amp;do=diff</link>
        <description>All wsrep-related (in this case - Galera) status variables are prefixed with 'wsrep_' so it is easy to check them with
mysql&gt; SHOW VARIABLES LIKE 'wsrep_%';
Status variables described in chapter 3 and below are differential and reset on every SHOW STATUS command. Thus it is recommended that two SHOW STATUS commands be executed on the node with an interval of ~1 minute and then the output of the last invocation will correspond to the current moment.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=mysql_galera_cluster_upgrade&amp;rev=1312576851&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-05T23:40:51+03:00</dc:date>
        <title>mysql_galera_cluster_upgrade</title>
        <link>http://www.codership.com/wiki/doku.php?id=mysql_galera_cluster_upgrade&amp;rev=1312576851&amp;do=diff</link>
        <description>This article discusses a situation where you might need to update the cluster software. Rolling upgrade is thought to be the alpha and omega of cluster software upgrade, but we'll looks at other possibilities too.

1. Rolling Upgrade

This is a type of upgrade everybody is talking about when they talk about “High Availability”. It is supposed to provide uninterruptible service during upgrade. The idea is that you</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=mysql_galera_howto&amp;rev=1332073773&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-18T14:29:33+03:00</dc:date>
        <title>mysql_galera_howto</title>
        <link>http://www.codership.com/wiki/doku.php?id=mysql_galera_howto&amp;rev=1332073773&amp;do=diff</link>
        <description>*  Galera cluster deployment variants
	*  MySQL/Galera cluster upgrade</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=mysql_options_0.7&amp;rev=1301530729&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-31T03:18:49+03:00</dc:date>
        <title>mysql_options_0.7</title>
        <link>http://www.codership.com/wiki/doku.php?id=mysql_options_0.7&amp;rev=1301530729&amp;do=diff</link>
        <description>These are MySQL system variables introduced by wsrep patch v0.8. All variables are global except where marked by (L).
 Option                          Default    Description  wsrep_auto_increment_control    ON         Automatically adjust auto_increment_increment and auto_increment_offset system variables when cluster membership changes.  wsrep_cluster_address                      Address to connect to cluster. Provider specific. Galera takes addresses in URL format:
&lt;backend schema&gt;://&lt;cluster …</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=mysql_options_0.8&amp;rev=1323574117&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-11T05:28:37+03:00</dc:date>
        <title>mysql_options_0.8</title>
        <link>http://www.codership.com/wiki/doku.php?id=mysql_options_0.8&amp;rev=1323574117&amp;do=diff</link>
        <description>These are MySQL system variables introduced by wsrep patch v0.8. All variables are global except where marked by (L).
 Option                          Default    Description  wsrep_auto_increment_control    ON         Automatically adjust auto_increment_increment and auto_increment_offset system variables when cluster membership changes.  wsrep_causal_reads (L)      OFF        Enforce strict cluster-wide “read committed” semantics on non-transactional reads. Results in larger read latencies.  ws…</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=node_failure&amp;rev=1307472175&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-07T21:42:55+03:00</dc:date>
        <title>node_failure</title>
        <link>http://www.codership.com/wiki/doku.php?id=node_failure&amp;rev=1307472175&amp;do=diff</link>
        <description>Node failure is probably the most important concept to understand in Galera clustering.

Galera cluster node can fail to operate for a variety of reasons: from hardware failure to software crash to loss of network connectivity and so on. All of these causes are generalized behind the concept of node failure and no distinction between them is made.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=node_provisioning_recovery&amp;rev=1307109450&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-03T16:57:30+03:00</dc:date>
        <title>node_provisioning_recovery</title>
        <link>http://www.codership.com/wiki/doku.php?id=node_provisioning_recovery&amp;rev=1307109450&amp;do=diff</link>
        <description>Both new and failed nodes have the same property in common: their state is different from the state of the primary component and needs to be synchronized. As a result, new node provisioning and failed node recovery are essentially the same process and boils down to the node joining the cluster primary component.</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=notification_command&amp;rev=1333621452&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-05T13:24:12+03:00</dc:date>
        <title>notification_command</title>
        <link>http://www.codership.com/wiki/doku.php?id=notification_command&amp;rev=1333621452&amp;do=diff</link>
        <description>If wsrep_notify_cmd is set, the server will try to invoke this command every time cluster membership or local node status changes. This can be used to (re)configure load balancers, raise alarm and so on.

Notification Command Arguments

The command will be passed one or more of the following options:</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=reference&amp;rev=1332549102&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-24T02:31:42+03:00</dc:date>
        <title>reference</title>
        <link>http://www.codership.com/wiki/doku.php?id=reference&amp;rev=1332549102&amp;do=diff</link>
        <description>Operation

Node Failure

Node Provisioning/Recovery

Galera Node State Machine

Flow Control

SSL Support

Galera Arbitrator

Scriptable State Snapshot Transfer

Writeset cache

Incremental State Transfer

Rolling Schema Upgrade (MySQL &gt;= 5.5.17 only)</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=rolling_schema_upgrade&amp;rev=1323574668&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-11T05:37:48+03:00</dc:date>
        <title>rolling_schema_upgrade</title>
        <link>http://www.codership.com/wiki/doku.php?id=rolling_schema_upgrade&amp;rev=1323574668&amp;do=diff</link>
        <description>Schema upgrade means any data definition statement (DDL statement) run for the database. They change the database structure and are non-transactional.

Total Order Isolation (TOI)

By default DDL processing in Galera happens by Total Order Isolation (TOI) method. With TOI, the DDL is processed in same order with regards to other transactions in each cluster node. With TOI method, the whole cluster has part of the database locked for the duration of the DDL processing (i.e. behaves like a single …</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=scriptable_state_snapshot_transfer&amp;rev=1325122566&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-29T03:36:06+03:00</dc:date>
        <title>scriptable_state_snapshot_transfer</title>
        <link>http://www.codership.com/wiki/doku.php?id=scriptable_state_snapshot_transfer&amp;rev=1325122566&amp;do=diff</link>
        <description>0.8 series MySQL/Galera introduces interface to customize state snapshot transfer via external script (or program). The script is to work under assumption that storage engine initialization on the receiving node happens after state transfer is complete. In short, the idea of this transfer is to copy the contents of source data directory to destination data directory (with possible variations).</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=ssl_support&amp;rev=1314391493&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-26T23:44:53+03:00</dc:date>
        <title>ssl_support</title>
        <link>http://www.codership.com/wiki/doku.php?id=ssl_support&amp;rev=1314391493&amp;do=diff</link>
        <description>Starting with version 0.8.2 Galera library supports SSL for encryption of replication traffic. It is a cluster-wide option and should be enabled either on all of the nodes or none at all. To use it a private certificate/key pair should be generated for a cluster, for example, by the following command</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=start&amp;rev=1297308785&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-02-10T05:33:05+03:00</dc:date>
        <title>start</title>
        <link>http://www.codership.com/wiki/doku.php?id=start&amp;rev=1297308785&amp;do=diff</link>
        <description>Terms and Concepts

wsrep API

Galera

0.8

MySQL/Galera cluster

0.8</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=state_transfer_protocol&amp;rev=1332073773&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-18T14:29:33+03:00</dc:date>
        <title>state_transfer_protocol</title>
        <link>http://www.codership.com/wiki/doku.php?id=state_transfer_protocol&amp;rev=1332073773&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=title_for_a_wiki_post&amp;rev=1332073773&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-18T14:29:33+03:00</dc:date>
        <title>title_for_a_wiki_post</title>
        <link>http://www.codership.com/wiki/doku.php?id=title_for_a_wiki_post&amp;rev=1332073773&amp;do=diff</link>
        <description>content for a wiki post</description>
    </item>
    <item rdf:about="http://www.codership.com/wiki/doku.php?id=wiki_editing_title&amp;rev=1332073773&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-18T14:29:33+03:00</dc:date>
        <title>wiki_editing_title</title>
        <link>http://www.codership.com/wiki/doku.php?id=wiki_editing_title&amp;rev=1332073773&amp;do=diff</link>
        <description>wiki editing content</description>
    </item>
</rdf:RDF>

