Tag Info

Hot answers tagged

11

Percona Server with XtraDB is the closest to the official MySQL Enterprise releases from Oracle. It is more conservative than MariaDB, which includes extra storage engines and more far-reaching code changes. (MariaDB is also built on the Percona XtraDB storage engine, but adds more changes to the rest of the MySQL server.) You should check out comparison ...


10

The root cause of this issue is that Red Hat broke binary compatibility of their OpenSSL packages between 6.4 and 6.5, something that they promised that they would not do. Resolving this problem is straightforward, but depending on the applications you may have deployed, may take some yelling at your application vendors. Be sure to reserve most of your ire ...


9

use mysqldump --opt <database> <tablename> to create a dump of your table and feed it to your new server. As you apparently have access to the remote database via TCP/IP, you simply could use mysqldump --opt --user=<youruser> --password=<yourpassword> -host <yourhost> \ <yourDB> <yourtable> | mysql -u ...


8

The data files are compatible with percona server. You just need to start percona server mysqld and everything will work. Only when you enable some features (like extra rollback segments) on percona server, you might not be able to go back to mysql. but you rarely need to change this parameter.


7

If you're using 100% InnoDB then you're in luck. You can use XtraBackup to make a full backup of your master database without any downtime or any table locking. This will be a consistent snapshot-style backup, the same as the sort that you get when you do the FLUSH TABLES WITH READ LOCK or --master-data options. The XtraBackup tool also drops an extra ...


6

The problem is not the limit on file handles. That would be error 24, not 13. The problem is what it says: permissions. I've seen this dozens of times, and even when people think that everything is set up correctly and has the right permissions, it IS permissions, every time, and someone always figures out that they missed something :) You either have ...


5

Based on your symptoms on node one, you are using wsrep_cluster_address=gcomm:// in your configuration file, which means the node will start a new cluster. You can confirm this with wsrep_cluster_size variable being 1 on node1, and 3 on the others. If you want to join node1 to your already existing cluster, you should specify ...


5

You can install PS 5.6 once you upgraded openssl to openssl-1.0.1e-15.el6.x86_64.rpm For 6.4 we (I work for Percona) also have some custom made packages available: http://www.percona.com/downloads/Percona-Server-5.5-centos-6.4/


5

The syslog option goes in the [mysql] section, not in the [mysqld] section, it's only for the client, not the server. So this does not provide any auditing of mysql commands, for that you need to enable query logging. For MySQL you'll find documentation here, I didn't find percona-specific documentation unfortunately.


4

Both platforms use the same mechanism for replication: Galera. On the page at that link, you'll notice there are images featuring both PXC and MariaDB Cluster. Galera library provides transactional replication. MyISAM doesn't do transactions, so the problems you may be having now are very likely related and would not be any different on the alternate ...


4

innodb_file_per_table That setting goes in the [mysqld] section not the [mysql] section in the /etc/my.cnf. If you move it to the correct section that issue will go away


4

Answer to Question 1 MySQL Replication suffers from two major problems MySQL Replication is Asynchronous. This may introduce replication delay. This manifests itself with communication problems between a Master and the Slave via the Slave I/O Thread. This may logically and numerically be seen in Seconds_Behind_Master. Data Drift. This is a intermittent ...


4

This question is a bit old now, but in case other people come across this page (like I did), here is what got me working: In my case the answer was apparmor. The solution: edit the file /etc/apparmor.d/usr.sbin.mysqld Add the following lines: /path/to/new/data/ r, /path/to/new/data/** rwk, /path/to/new/logs/ r, /path/to/new/logs/ rw, Then restart ...


3

but I thought the whole point of replication was to take care of the synchronization of data for you Yes, MySQL replication does try to synchronize a replicated database. However, MySQL replication is tricky and the replication can fail for various reasons. Replication errors in my experience are rare, but they do happen during unexpected server ...


3

It sounds like log_queries_not_using_indexes is enabled. Check it by doing: mysql> show global variables like 'log_queries%'; +-------------------------------+-------+ | Variable_name | Value | +-------------------------------+-------+ | log_queries_not_using_indexes | ON | +-------------------------------+-------+ Turn it off with: ...


3

The display of the error log looks quite normal Socket file was created MySQL Replication started just fine /usr/sbin/mysqld: ready for connections. appears Especailly since you see /usr/sbin/mysqld: ready for connections., you should be able to connect to mysql which you just stated that you can. Your mysqld process is fine. The error may be coming from ...


3

It appears that the init script checks for a running MySQL/Percona server on Ubuntu by using mysqladmin --defaults-file=/etc/mysql/debian.cnf ping (see line 27 and 77 of /etc/init.d/mysql of the in this case percona-server-server-5.5 package version 5.5.28-rel29.2-360.precise). This works in a default new installation, but when copying over data files in ...


3

I work for Percona, so I'm biased. I'd say that while on the surface they are similar products, PXC has had many more releases, we're doing a ton more QA, and are doing much more to contribute back to Codership than Maria so far. However, MyISAM support is going to be the same on either, and I'm sorry to say that if MyISAM is a design requirement for you, ...


3

You probably need to download and install these packages: http://www.percona.com/downloads/Percona-Server-5.0/LATEST/RPM/rhel6/i686/ It seems you are trying to install RHEL5 package to RHEL6 system. You can verify this by typing: cat /etc/redhat-release


3

When you connect to MySQL, just run SELECT SUBSTR(variable_value,1, LOCATE(' ',variable_value) - 1) DBVersion FROM information_schema.global_variables WHERE variable_name='version_comment'; You should get this when you connect to MySQL mysql> SELECT SUBSTR(variable_value,1, -> LOCATE(' ',variable_value) - 1) DBVersion -> FROM ...


3

No because the above mentioned --apply-log won't update LSN in xtrabackup_checkpoints, thus every next incremental backup will copy pages modified since the last full backup. That's not what you want to achieve UPD To implement your scenario you need: Take full backup innobackupex --no-timestamp /path/full Save the last LSN # cat ...


3

The first point to remember here is many mysql clients (including php) will default to unix socket style communication if the client is configured to use localhost. If your server is not correctly setting up this socket, then clients may be attempting to connect to the socket and failing. The rest is summarized from our discussion in the comments. In any ...


3

Well shame on me, I was able to install Percona Shared Compat to get rid of this issue: Percona-Server-shared-compat.x86_64 I hope this helps others.


2

It looks like the packages provided by remi aren't compatible with the ones supplied by Percona. Fortunately it looks like Percona supply the packages too yum list | grep percona | grep devel Percona-SQL-devel-50.x86_64 5.0.92-b23.89.rhel6 percona Percona-Server-devel-51.x86_64 5.1.73-rel14.11.603.rhel6 percona ...


2

Replication is for availability,you might be interested in things like pacemaker clustering and the Percona mysql resource agent to manage replication and provide automatic failover. Considering innobackupex, it is primary a backup utility, replication might go wrong, in that case you'll be happy to have a fast way of recovery. Hope this helps.


2

I would start by enable mysql_long_queries, and then examine the log output. in my.cnf under [mysqld] long_query_time = 1 log-slow-queries = /var/log/mysql/mysql_slow.log and go from there. You can also use: show processlist show full processlist to see which queries are currently running.


2

The problem is that Percona by default uses eth0 unless overridden. It uses the following command to work out the ip address it should communicate on: /sbin/ifconfig | grep -E '^[[:space:]]+inet addr:' | grep -m1 -v 'inet addr:127' | sed 's/:/ /' | awk '{ print $3 }' Which results in 10.0.2.15. The wsrep_node_address variable can be set which tells it ...


2

Run the following command mysqladmin variables | grep version_comment | awk '{print $2}'


2

mysql_install_db chown -R mysql:mysql /yourdatadir service mysql start This should do the job for you.


2

If you want to take incremental backup use innobackupex Creating an Incremental Backups with innobackupex First, you need to make a full backup as the BASE for subsequent incremental backups: $ innobackupex /data/backups This will create a timestamped directory in /data/backups. Assuming that the backup is done last day of the year, BASEDIR would be ...



Only top voted, non community-wiki answers of a minimum length are eligible