Tag Info

Hot answers tagged

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

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


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

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

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

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

What if you change this part in my.cnf [MYSQLD_SAFE] pid_file=mysqld.pid to be [MYSQLD_SAFE] pid_file=/var/lib/mysql/mysqld.pid I guess systemd did kill MySQL because it did not find a proper pid file containing a process number in that location.


2

Just have your development server connect using normal replication, not join the cluster. Standard replication is one way (unless you set it up on both sides). Your dev server would pull the binlogs from the master it's slaving from. That's all the communication that would happen between the dev instance and your cluster. I don't think there would be an ...


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

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


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

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

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


2

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


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

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


1

Maybe you could get at it the other way - try to find which my.cnf is percona trying to read. ie. mysqld --help --verbose | head -n 30 and look for something like Default options are read from the following files in the given order: /etc/mysql/my.cnf ~/.my.cnf


1

If you ignore dependencies or just try to satisfy with random packages you find, you'll just find yourself in 'RPM hell.' Just because it's an RPM doesn't mean it works with your distribution. Percona does have a yum repository. I suggest you follow those directions, assuming that you're using either CentOS or RedHat. Then installing percona will be as ...


1

problem 1 You are installing a rpm for 5.x on a 6.x system from what I can tell problem 2 .. Install their yum repo and install that way Follow the steps here http://www.percona.com/docs/wiki/repositories:yum


1

It isn't that hard to install percona. Just read the following http://www.percona.com/doc/percona-server/5.5/installation.html?id=percona-server:installation:from-repositories It is really just installing the yum repo and running a few commands.. Yes there are some instances. Don't be lazy and search for them. Here's a few in us-east-1 ami-61c16908 - ...


1

NEver mind , i copied the files from /var/lib/mysql to the new location.


1

Use innodb_file_per_table in the following way under [mysqld] section in my.cnf [mysqld] innodb_file_per_table


1

We have a separate database we use for sessions which was configured to use persistant connections from PHP, and that's where the error message was coming from. Turning off persistant connections may turn out to be the answer after all. The above comes from not being able to find anything unusually bad with the configuration for the main database.



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