Re: MMM Mysql
On Thu, Jul 22, 2010 at 8:42 PM, Kyong Kim kykim...@gmail.com wrote: Has anyone used this in production? We're looking at this as part of our sharding/scale strategy and wanted some insight into real world experience. Are there alternatives out there? Kyong Lots of people are using MMM. Alternatives include Linux-HA (aka heartbeat) often combined with DRBD and MySQL cluster. For the general case MMM is probably the best option. -- Rob Wultsch wult...@gmail.com
Command MySQL Check
Hi, I want to check daily a large database. If I execute a mysqlcheck, its execution is longer the 8 minutes. What is the best practice to check tables daily ? medium option? Fast option? Regards, David
MySQL Community Server 5.1.49 has been released
Dear MySQL users, MySQL Community Server 5.1.49, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.49 is recommended for use on production systems. For an overview of what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.49 on new servers or upgrading to MySQL 5.1.49 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html Enjoy! === C.1.2. Changes in MySQL 5.1.49 (09 July 2010) InnoDB Notes: * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History (http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-changes. html), may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Replication: When using unique keys on NULL columns in row-based replication, the slave sometimes chose the wrong row when performing an update. This happened because a table having a unique key on such a column could have multiple rows containing NULL for the column used by the unique key, and the slave merely picked the first row containing NULL in that column. (Bug#53893: http://bugs.mysql.com/bug.php?id=53893) * Replication: FLUSH LOGS could in some circumstances crash the server. This occurred because the I/O thread could concurrently access the relay log I/O cache while another thread was performing the FLUSH LOGS, which closes and reopens the relay log and, while doing so, initializes (or re-initializes) its I/O cache. This could cause problems if some other thread (in this case, the I/O thread) is accessing it at the same time. Now the thread performing the FLUSH LOGS takes a lock on the relay log before actually flushing it. (Bug#53657: http://bugs.mysql.com/bug.php?id=53657) See also Bug#50364: http://bugs.mysql.com/bug.php?id=50364. * Replication: Two related issues involving temporary tables and transactions were introduced by a fix made in MySQL 5.1.37: 1. When a temporary table was created or dropped within a transaction, any failed statement that following the CREATE TEMPORARY TABLE or DROP TEMPORARY TABLE statement triggered a rollback, which caused the slave diverge from the master. 2. When a CREATE TEMPORARY TABLE ... SELECT * FROM ... statement was executed within a transaction in which only tables using transactional storage engines were used and the transaction was rolled back at the end, the changes---including the creation of the temporary table---were not written to the binary log. The current fix restores the correct behavior in both of these cases. (Bug#53560: http://bugs.mysql.com/bug.php?id=53560) This regression was introduced by Bug#43929: http://bugs.mysql.com/bug.php?id=43929. * Replication: When CURRENT_USER() or CURRENT_USER was used to supply the name and host of the affected user or of the definer in any of the statements DROP USER, RENAME USER, GRANT, REVOKE, and ALTER EVENT, the reference to CURRENT_USER() or CURRENT_USER was not expanded when written to the binary log. This resulted in CURRENT_USER() or CURRENT_USER being expanded to the user and host of the slave SQL thread on the slave, thus breaking replication. Now CURRENT_USER() and CURRENT_USER are expanded prior to being written to the binary log in such cases, so that the correct user and host are referenced on both the master and the slave.
Archive data from a single partition
I have a very large table (over 2 billion rows) which is partitioned by day. I'd like to archive all the data in the oldest partition to another table before I drop that partition. Is there some way other than a simple select statement that has parameters that match those of the partition whic will allow me to copy all data in a single partition over to another table? Thanks, Bryancan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Setting Up MySSQL replication with SSL on Ubuntu and Windows
Hi! a.sm...@ukgrid.net schrieb: According to this you must install OpenSSL then compile MySQL from source http://dev.mysql.com/doc/refman/5.0/en/secure-basics.html You cannot (in general) assume that some hint you find somewhere for MySQL 5.0 still applies to MySQL 5.1. Specifically if the source is the MySQL manual, there is absolutely no reason to use the 5.0 manual when you are dealing with 5.1, there is a 5.1 manual available. Would be nice if someone on the list with prior experience would comment Discussing SSL: it is included with current versions of MySQL 5.1 on Windows. Sadly, 5.1.46 is a special case: When testing it, there was trouble on the machines, so the SSL tests were not attempted. Definitely, both 5.1.45 and 5.1.47 include SSL and passed the tests. My hint to Neil: Try to run the MySQL test suite on your machine, it includes SSL tests. If these pass, your server (and client) does include SSL. Quoting Tompkins Neil neil.tompk...@googlemail.com: Hi I found this documentation. However, I need more information on setting up SSL on Windows ? I don't deal with Windows, so I can't help with this. Regards, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com (+49 30) 417 01 487 ORACLE Deutschland B.V. Co. KG, Komturstrasse 18a, D-12099 Berlin Geschaeftsfuehrer: Juergen Kunz, Marcel v.d. Molen, Alexander v.d. Ven Amtsgericht Muenchen: HRA 95603 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
recovering database from rescue mode
Hello,
I have a server which has been booted in rescue mode, i have copied
the /mnt/var/lib/mysql/blog folder to another server running MySQL and
copied this folder to /var/lib/mysql
when i connect to the mysql cli, i get this:
http://pastie.org/1057117
but my source server is 64bit where as the target machine is 32bit
should this cause the issue?
what is the way to get these files on to the new server?
thanks
--
˙uʍop ǝpısdn p,uɹnʇ pןɹoʍ ǝɥʇ ǝǝs noʎ 'ʇuǝɯɐן sǝɯıʇ ǝɥʇ puɐ 'ʇuǝʇuoɔ
ǝq s,ʇǝן ʇǝʎ
% .join( [ {'*':'@','^':'.'}.get(c,None) or
chr(97+(ord(c)-83)%26) for c in ,adym,*)uzq^zqf ] )
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Replication: ignore specified columns?
I know that you can ignore certain databases and tables in mysql replication, but is it possible to replicate all but a certain column or two from a table? This is 5.1.48 on linux. Thanks, Bryancan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Replication: ignore specified columns?
No. If it is for security reasons: did you think about a view on slave db? (removing rights from source table) In case you dont want those columns to reach the slave you could use triggers to reflect changes from source table (or a view) on master to a table(with missing columns) that will be replicated. Just a couple of ideas Claudio 2010/7/23 Bryan Cantwell bcantw...@firescope.com I know that you can ignore certain databases and tables in mysql replication, but is it possible to replicate all but a certain column or two from a table? This is 5.1.48 on linux. Thanks, Bryancan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=claudio.na...@gmail.com -- Claudio
Re: MMM Mysql
Are there any known issues or challenges implementing MMM? We're currently focused on MMM but just kinda wanted to keep our eyes open. Kyong On Thu, Jul 22, 2010 at 11:19 PM, Rob Wultsch wult...@gmail.com wrote: On Thu, Jul 22, 2010 at 8:42 PM, Kyong Kim kykim...@gmail.com wrote: Has anyone used this in production? We're looking at this as part of our sharding/scale strategy and wanted some insight into real world experience. Are there alternatives out there? Kyong Lots of people are using MMM. Alternatives include Linux-HA (aka heartbeat) often combined with DRBD and MySQL cluster. For the general case MMM is probably the best option. -- Rob Wultsch wult...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MMM Mysql
It kind of depends on your application. If you have an application like most web applications, it is okay to skip a beat and a half when a failover occurs. Usually you can lose a very small number of transactions (the ones that are ongoing when the failure occurs), but your failover happens sub-second or very close to that. For most web applications it is more important that service continues, and it is acceptable to lose a few transactions (these will just have to be tried again). Other then that 1. make sure to use a separate machine for the monitor 2. make sure that if you use VM's, you put your masters on different physical machines 3. make sure that ARP traffic can flow freely between your machines. EC2 doesn't support thatfor instance, so you'll either have to stick with MMM 1 or patch MMM 2. That's the most important part I think :) Walter Heck Engineer @ OpenQuery (http://openquery.com) On Sat, Jul 24, 2010 at 07:59, Kyong Kim kykim...@gmail.com wrote: Are there any known issues or challenges implementing MMM? We're currently focused on MMM but just kinda wanted to keep our eyes open. Kyong On Thu, Jul 22, 2010 at 11:19 PM, Rob Wultsch wult...@gmail.com wrote: On Thu, Jul 22, 2010 at 8:42 PM, Kyong Kim kykim...@gmail.com wrote: Has anyone used this in production? We're looking at this as part of our sharding/scale strategy and wanted some insight into real world experience. Are there alternatives out there? Kyong Lots of people are using MMM. Alternatives include Linux-HA (aka heartbeat) often combined with DRBD and MySQL cluster. For the general case MMM is probably the best option. -- Rob Wultsch wult...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=li...@olindata.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
