mysql

TwitterFacebook
Get flash to fully experience Pearltrees
This tutorial describes how to set up MySQL master-master replication. We need to replicate MySQL servers to achieve high-availability (HA). In my case I need two masters that are synchronized with each other so that if one of them drops down, other could take over and no data is lost. Similarly when the first one goes up again, it will still be used as slave for the live one.

MySQL Master Master Replication | HowtoForge - Linux Howtos and

http://www.howtoforge.com/mysql_master_master_replication
http://bakery.cakephp.org/articles/eagerterrier/2007/05/26/load-balancing-and-mysql-master-and-slaves-2 If you are currently using MySql master/slave replication for load balancing and wish to transport to cakePHP, it really couldn't be easier. However, there are some instance where you may want to use a query in your controller where you update/insert information. In this case, use the following: I use this where I want information to be updated, but don't want cake to flush the cache. But then again, that may be like crossing the streams in Ghostbusters, so don't listen to me..

Load Balancing and MySQL Master and Slaves (Articles) | The Bake

This tutorial shows how to configure a MySQL 5 cluster with three nodes: two storage nodes and one management node. This cluster is load-balanced by a high-availability load balancer that in fact has two nodes that use the Ultra Monkey package which provides heartbeat (for checking if the other node is still alive) and ldirectord (to split up the requests to the nodes of the MySQL cluster). In this document I use Debian Sarge for all nodes. Therefore the setup might differ a bit for other distributions. http://www.howtoforge.com/loadbalanced_mysql_cluster_debian

How To Set Up A Load-Balanced MySQL Cluster | HowtoForge - Linux

Ultra Monkey:

http://www.ultramonkey.org/ heartbeat update (1.2.3.cvs.20050927-1bpo4 / 1.2.3.cvs.20050927-1.rh.el.um.4) New heartbeat packages have been made available for Ultra Monkey 3 on both Red Hat Enterprise Linux 3 [offsite] and Debian Sarge [offsite] in order to address a bug in ldirectord which caused it to die when connect checks were used. The current release is Ultra Monkey 3 which has been built and tested on Debian Sarge and Red Hat Enterprise Linux 3.0.
Home > MySQL > If you get this in MySQL Lock wait timeout exceeded; try restarting transaction I ran into this crap when I needed to purge a massive number of records from a database. All you need to do is edit the timeout setting in your MySQL config file. If you make this change on a production server you may want to set it back to the default setting. I don’t know what the consequences of a long timeout setting would be.

If you get this in MySQL Lock wait timeout exceeded; try restart

http://www.tonyspencer.com/2008/10/23/if-you-get-this-in-mysql-lock-wait-timeout-exceeded-try-restarting-transaction/
I configured MySQL’s my.cnf file to use the tuning setup from the my-medium.cnf, which should give us good tuning parameters for our load at this point. Then I added the pieces necessary for replication in both DB-1 and DB-2: Warning : I’ve changed default path of MYSQL data directory to /data/mysql, so you need to change it to your data directory. (default path is /var/lib/mysql/) 1. On Both Servers, you need to create a replication slave account in mysql: http://linax.wordpress.com/2010/03/20/centos-mysql-master-master-repliction/

Mysql Master Master Repliction « Nasser Heidari

By default, MySQL's datadir is placed in the /var/lib/mysql directory. However, if you are planning on using MySQL tables to store a lot of data and your /var partition is small, it might cause you problem at a later stage. In such a scenario, it is better to move the MySQL's datadir to another partition (like /home . copy the files from the old datadir to the new location. However, make sure that the files named ib_arch_log_0000000000, ib_logfile0 etc. are not copied to the newer location. http://rajshekhar.net/blog/archives/90-Moving-the-MySQLs-datadir-directory.html

Moving the MySQL's datadir directory. - lunatechian (lunatech-ia

How to move MySQL datadir to another drive | Kaliphonia.com

http://www.kaliphonia.com/content/linux/how-to-move-mysql-datadir-to-another-drive [root@server ~]# ls -o /var/lib/mysql -rw-rw---- 1 mysql 10485760 Jul 9 19:04 ibdata1 -rw-rw---- 1 mysql 5242880 Jul 9 19:04 ib_logfile0 -rw-rw---- 1 mysql 5242880 Jul 9 07:13 ib_logfile1 drwx------ 2 mysql 4096 Jul 15 07:40 joomla drwx------ 2 mysql 4096 Jul 9 06:03 mysql srwxrwxrwx 1 mysql 0 Aug 13 09:42 mysql.sock drwx------ 2 mysql 4096 Jul 9 11:31 users drwx------ 2 mysql 4096 Jul 9 08:22 wordpress [root@server ~]# Copy only databases from current MySQL datadir to the new directory recursively. Remember to copy database only, do not copy ibdata*, ib_logfile*, mysqld-log-bin or mysqld-log-bin.* files!
Black Duck plans to integrate the SpikeSource products and services into its offerings. The SpikeForge open source projects are being migrated to other forges, and we’re encouraging members of the Developer Zone to join developers on Ohloh.net , Black Duck’s open source project directory and community. As mentioned on the Developer Zone homepage, we will be discontinuing the SpikeSource website and the Developer Zone starting January 9, 2011.

How to change the mysql database location - Spike Developer Zone

http://www.blackducksoftware.com/spikesource/

Top 20+ MySQL Best Practices | Nettuts+

Database operations often tend to be the main bottleneck for most web applications today. It’s not only the DBA’s (database administrators) that have to worry about these performance issues. We as programmers need to do our part by structuring tables properly, writing optimized queries and better code. Here are some MySQL optimization techniques for programmers. 1. Optimize Your Queries For the Query Cache http://net.tutsplus.com/tutorials/other/top-20-mysql-best-practices/
…and other MySQL Oddities. If your MySQL binary log files are a “Growing” problem… there are a few simple steps you can use to curtail their growth and save your disk space from these huge files. The first is to stop the MySQL server from creating these binary files. The only reason you would need the binary log files is if you are doing mysql replication from a master to a slave. In this case, these files are necessary, at least until the slave(s) has caught up with the master. To stop this from logging, comment out (using #) the line containing ‘log-bin’.

My MySQL Binary Log files are taking up all my disk space! – sys