no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | percona_xtradb_cluster_deployment [2012/05/19 00:49] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Percona XtraDB Cluster Deployment ====== | ||
+ | * [[Percona XtraDB Cluster]] | ||
+ | |||
+ | **ALL TABLES MUST USE INNODB** or the feature set is thrown out the window. | ||
+ | |||
+ | In each case, **do not** create a '' | ||
+ | |||
+ | When you initially install the Percona database, use the same root password across nodes to begin with. When syncing begins, the mysql database will be overriden anyway, so to avoid confusion, keep it the same on setup across all nodes. | ||
+ | |||
+ | The first thing to do is setup a primary node. You'll need the configuration file from the main wiki page. | ||
+ | |||
+ | Open a firewall rule so that the secondary nodes can access MySQL directly. | ||
+ | |||
+ | Startup the primary node, and watch the error log closely for any warnings that may arise. | ||
+ | |||
+ | Once the master node is setup, you can move to the secondary ones. Use the same config file from the original server, making the small modifications for the node. Startup the node, and **be patient** as it takes some time for the initial startup and sync -- the mysql socket file won't be available for a few seconds to a minute. | ||
+ | |||
+ | Each Ubuntu installation creates an admin MySQL configuration file in ''/ | ||
+ | |||
+ | Go ahead and create some test databases or tables to verify synchronization. |