Questions[xtradb](server)

All the good days. I want to run for test purposes Percona XtraDb Cluster on ubuntu 14.04. The basis here took these two articles

1. https://habrahabr.ru/post/152969/
2. https://www.percona.com/doc/percona-xtradb-cluster/5.6/manual/bootstrap.html

I came instead

Ну и в завершение, перезапускаем демона:

The daemon does not start

$ sudo /etc/init.d/mysql start  
 * Starting MySQL (Percona XtraDB Cluster) database server mysqld 
 * The server quit without updating PID file (/var/lib/mysql/vagrant-ubuntu-trusty-64.pid).
   ...fail! 

The logs several errors. Error one:

[ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.

Sure I ran mysql_upgrade, but it does not work

$ sudo mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck FATAL ERROR: Upgrade failed

Error two:

160502 14:56:26 [ERROR] Plugin 'InnoDB' init function returned error. 160502 14:56:26 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 160502 14:56:26 [ERROR] Unknown/unsupported storage engine: InnoDB 160502 14:56:26 [ERROR] Aborting

All are advised to remove all of the folders / var / lib / mysql and supposedly starts. But I deleted and nothing worked.

My file my.cnf

[mysqld_safe]
# wsrep_urls=gcomm://192.168.33.101:3400,gcomm://192.168.33.102:3400,gcomm://
#wsrep_urls=gcomm://192.168.33.101:3400,gcomm://

[mysqld]
innodb_log_file_size=256M
wsrep_cluster_address=gcomm://192.168.33.101
port=3306
socket=/var/run/mysqld/mysqld.sock
datadir=/var/lib/mysql
basedir=/usr
user=mysql
log_error=/var/log/mysql.err
binlog_format=ROW
default_storage_engine=InnoDB
wsrep_provider=/usr/lib/libgalera_smm.so
wsrep_sst_receive_address=192.168.33.101:3500
wsrep_node_incoming_address=192.168.33.101
wsrep_slave_threads=2
wsrep_cluster_name=cluster0
wsrep_provider_options="gmcast.listen_addr=tcp://192.168.33.101:3400;"
wsrep_sst_method=xtrabackup
wsrep_sst_auth=backup:password
wsrep_node_name=node0
innodb_locks_unsafe_for_binlog=1
innodb_autoinc_lock_mode=2
innodb_buffer_pool_size=5000M
innodb_log_file_size=256M
innodb_log_buffer_size=4M

[client]
port=3306
socket=/var/run/mysqld/mysqld.sock

Actually the question: how to start? If there is anyone working configuration, then please share.

I have been reviewing XtraDB clustering and produced a P.o.C. environment on Openstack using 4 instances, which has fallen over during my resilience testing.

Per the pxc documentation: http://www.percona.com/doc/percona-xtradb-cluster/howtos/virt_sandbox.html which covers a 3 node install I opted for a 4th.

1. Initial setup complete data loading tests passed, with all nodes being updates synchronously using a 1.6GB test sql file to load a database.
2. Failiure and restore of nodes commenced, this test entailed stoping the mysql service on a node, creating and subsequently dropping a database to test surviving node replication, and starting of the downed node to resync.
   1. This worked fine for nodes 4,3,2.
   2. Node1 which per the pxc documents is essentially a controller, would not rejoin the cluster.

So my questions are as follows:

1. How to return a controller node to service if surviving nodes have since had data written to them
2. Using 4 nodes as a reference, is there a way to remove this single point of failure in node1? (if a surviving node restarts with the controller (node1) down/out of sync, that node will also fail).

I am preparing for setting up a MySQL master-slave or master-master relationship. Right now I have a single MySQL production server, and of course I don't want a lot of downtime while I connect the slave.

Is there no way I can make connect an empty slave and let it "slowly" synchronize data from the master, until they are identical?

I have noticed that I can take a transactional dump with mysqldump on the master and then import that into the slave, but by the time the slave has imported the dump, a lot of new rows will have been written and how will the slave get these?

I hope I am missing something obvious here, but extensive googling gives such advice such as "since this will result in less downtime in the future, some downtime now maybe isn't such a bad thing". But I would really like to avoid that.

Related question for MyISAM, but I use InnoDB.

I'm running MySQL 5.0 in production on CentOS. How do I migrate to Percona Server 5.1 safely?

The documentation of Percona Server doesn't include any information on migrating. Any help is greatly appreciated.

I'm working on a social website with an approximate read/write split of 90/10. Trying to decide on a MySQL engine. The ones I'm interested in are:

1. XtraDB
2. PBXT
3. TokuDB

What are the pros and cons of them for my use case?

A few specific questions:

• PBXT uses log-based structure that avoids double-writes. It sounds very elegant, but the benchmark I've seen doesn't show any/much advantages over XtraDB. Do you have any experience with PBXT/XtraDB you can share?

• TokuDB sounds VERY interesting. But all the benchmarks I've seen are about single-threaded bulk inserts - inserting 100M rows for example. that's not very relevant for OLTP. What about its performance with large number of concurrent threads writing and reading at the same time running on multiple cores? Anyone has tried that?