Tag Info

Hot answers tagged

10

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 ...


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 ...


9

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 ...


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 ...


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

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.


5

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

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.


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/


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 ...


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

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 ...


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

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 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

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

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

As taken from the first line of the Percona Server website: Percona Server with XtraDB is a backwards-compatible replacement for MySQL that is much faster and more scalable... It's backwards-compatible, so you just use it like you use any installation of mysql. Same commands, same flags, etc. I'd get a grip of the basics of a standard mysql setup before ...


2

The CLI commands are all the same. In fact, everything is the same. Percona is MySQL with some internal tweaks.


2

libmysqlclient18 : Depends: mysql-common (>= 5.5.18-1~dotdeb.1) This error here seems to strongly indicate what your problem is. You appear to mixing and matching several different repositories. It appears you have at least the official, percona, and dotdeb repositories. Somehow you have gotten into a state where it seems like the dotdeb ...


2

Yes, the mysqld will be removed when you do a yum remove. You could copy/hardlink the file with the new name before the removing, but since I guess there is more replaced with this update than just the mysql demon executable, I think the better way is to make sure you have a working backup of your data and configuration files before you start and do the ...


2

It is not possible to start a mysql replication "from scratch". Instead, you could use mysqldump with the --master-data=2 parameter when dumping your databases - i.e. like this: mysqldump --master-data=2 --all-databases --opt -p > myinitialdump.sql This command will lock all tables within the affected databases during the dump and write the ...


2

This is how I solved this problem: Get the public IP address of RDS endpoint $ nslookup rdsbench.c2dddddddx.us-east-1.rds.amazonaws.com Address: 10.271.12.X Add this IP address along with your favourite alias name to /etc/hosts file 10.271.12.X mybenchdb


2

You can setup a local DNS server to resolve it to a shorter name. If you are connecting from a bash shell, you could also do, $ export mybenchdb="rdsbench.c2wfqsdsqd.us-east-1.rds.amazonaws.com" $ mysql -h$mybenchdb Add the export to .profile or .bash_profile and it should be permanent.


2

Don't know why the Percona-XtraDB-Cluster-galera is missing from the Percona repo. But you can compile from source code. First, download and install Galera wsrep provider: Name : galera Relocations: (not relocatable) Version : 23.2.1 Vendor: Codership Oy Release : 1.rhel5 ...


2

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 ...


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 ...



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