restrict mysql replication ?
I have a need to have a number of small tables (perhaps up to 1 rows each) replicated to a number of mysql slaves. Frequency of change is very low, and they need not be replicated within seconds, an hour is fine. The master server has a lot more and bigger tables, but each slave will only have a small subset of those. I've held off setting up proper replication, thinking it was too much effort, but I've now just yesterday set up one such replication. I've got the slave only replicating two tiny, mostly static tables, so I had kind of expected not to see a lot of network traffic. Instead I see lots and lots of replication traffic? I'm guessing the master notifies the slave(s) of all changes, not just changes to the replicated tables? Is there a way of limiting that? Alternatively, is there a way of doing replication-on-demand, perhaps triggered by cron? /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: restrict mysql replication ?
Per Jessen wrote: Is there a way of limiting that? Alternatively, is there a way of doing replication-on-demand, perhaps triggered by cron? Ignore this, problem solved. I'll let the slaves query the master regularly and just reload the entire table. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: restrict mysql replication ?
On Wed, Dec 15, 2010 at 10:08 AM, Per Jessen p...@computer.org wrote: Per Jessen wrote: Is there a way of limiting that? Alternatively, is there a way of doing replication-on-demand, perhaps triggered by cron? Ignore this, problem solved. I'll let the slaves query the master regularly and just reload the entire table. That works. As for what you're seeing, you're probably limiting replication on the slave instead of limiting binlogging on the master. Can't quite recall the exact option, something like binlog-do-db I think. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: restrict mysql replication ?
Johan De Meersman wrote: On Wed, Dec 15, 2010 at 10:08 AM, Per Jessen p...@computer.org wrote: Per Jessen wrote: Is there a way of limiting that? Alternatively, is there a way of doing replication-on-demand, perhaps triggered by cron? Ignore this, problem solved. I'll let the slaves query the master regularly and just reload the entire table. That works. As for what you're seeing, you're probably limiting replication on the slave instead of limiting binlogging on the master. Yes, that sounds like what I'm doing. Can't quite recall the exact option, something like binlog-do-db I think. Thanks for the hint, might still come in useful. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
[NEWS]
Hello! Hello! I'd like to place basic information about our products. I'll be appreciate you. Best Regards, Sergey Lazurenko CodeCompare 2.50.odt Description: application/vnd.oasis.opendocument.text -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Community Server 5.5.8 has been released
Dear MySQL users, We are proud to present to you the MySQL Database 5.5.8 GA release, the first 5.5 production version of the world's most popular open source database. MySQL 5.5.8 is recommended for use on production systems. MySQL 5.5 includes several high-impact changes to address scalability and performance issues in MySQL Database. These changes exploit advances in hardware and CPU design and enable better utilization of existing hardware. MySQL 5.5 also provides a number of other new enhancements, including: - InnoDB I/O Subsystem Changes - Enhanced Solaris Support - Diagnostic and Monitoring Capabilities For a more complete look at what's new in MySQL 5.5, please see http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html If you are running a MySQL production level system, we would like to direct your attention to the product description of MySQL Enterprise Edition at: http://mysql.com/products/enterprise/ For information on installing MySQL 5.5.8 on new servers, please see the MySQL installation documentation at http://dev.mysql.com/doc/refman/5.5/en/installing.html For upgrading from previous MySQL releases, please see the important upgrade considerations at: http://dev.mysql.com/doc/refman/5.5/en/upgrading.html MySQL Database 5.5 is available in source and binary form for a number of platforms from our download pages at: http://mysql.com/downloads/mysql/ 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 The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.5. It may also be viewed online at: http://dev.mysql.com/doc/refman/5.5/en/news-5-5-8.html D.1.1. Changes in MySQL 5.5.8 (03 December 2010) Configuration Notes: * MySQL releases are now built on all platforms using CMake rather than the GNU autotools, so autotools support has been removed. For instructions on building MySQL with CMake, see Section 2.11, Installing MySQL from Source. Third-party tools that need to extract the MySQL version number formerly found in configure.in can use the VERSION file. See Section 2.11.6, MySQL Configuration and Third-Party Tools. Functionality added or changed: * Support for the IBMDB2I storage engine has been removed. (Bug#58079: http://bugs.mysql.com/bug.php?id=58079) * A --bind-address option has been added to a number of MySQL client programs: mysql, mysqldump, mysqladmin, mysqlbinlog, mysqlcheck, mysqlimport, and mysqlshow. This is for use on a computer having multiple network interfaces, and enables you to choose which interface is used to connect to the MySQL server. Bugs fixed: * Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables. (Bug#53046: http://bugs.mysql.com/bug.php?id=53046) * Incompatible Change: Previously, tables in the performance_schema database had uppercase names. This was incompatible with the lower_case_table_names system variable, and caused issues when the variable value was changed after installing or upgrading. Now performance_schema table names are lowercase, so they appear in uniform lettercase regardless of the lower_case_table_names setting. References to these tables in SQL statements should be given in lowercase. This is an incompatible change, but provides compatible behavior across different values of lower_case_table_names. If you upgrade to MySQL 5.5.8 from an earlier version of MySQL 5.5, be sure to run mysql_upgrade (and restart the server) to change the names of existing performance_schema tables from uppercase to lowercase. (Bug#57609: http://bugs.mysql.com/bug.php?id=57609) * Incompatible Change: The following changes were made to the performance_schema.threads table for conformance with the implementation in MySQL 5.6: + ID column: Renamed to PROCESSLIST_ID, removed NOT NULL from definition. + NAME column: Changed from VARCHAR(64) to VARCHAR(128). (Bug#57154: http://bugs.mysql.com/bug.php?id=57154) * Incompatible Change: Deadlock occurred when a connection that had some table open through a HANDLER statement tried to update data through a DML statement while another connection tried to execute FLUSH TABLES WITH READ LOCK concurrently. Starvation of FLUSH TABLES WITH READ LOCK statements occurred when there was a constant load of concurrent DML statements in two or
Re: Bulk Insertion Performance
On Dec 14, 2010, at 7:21 PM, Feris Thia wrote: Hi Mark, On Wed, Dec 15, 2010 at 8:10 AM, Mark Matthews mark.matth...@oracle.com wrote: Feris, *How* are you writing, via batch statements with rewriting, or directly, or via LOAD DATA INFILE? It seems you're off by about a factor of 10-20x from what I've seen performance-wise for writes. I'm using ETL mean - for this case, it is a java application name Kettle (Pentaho Data Integration). And it use JDBC connection. Is it a JDBC driver configuration ? Feris, I don't know what Kettle is doing under the hood, but if it's doing addBatch(), executeBatch(), then adding rewriteBatchedStatements=true to your MySQL JDBC URL should probably help quite a bit. -Mark -- Mark Matthews Principal Software Developer - MySQL Enterprise Tools Oracle http://www.mysql.com/products/enterprise/monitor.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: [NEWS]
On Wed, 2010-12-15 at 14:06 +0200, Sergey Lazurenko wrote: Hello! Hello! I'd like to place basic information about our products. I'll be appreciate you. Best Regards, Sergey Lazurenko -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=noel.but...@ausics.net hello! thank you very much! I unfortunately did not, and will not, take the time to read your spam, but please rest assured relevant sender IP and domains are now entered into a DNSBL Again, thank you very much, and Merry Christmas signature.asc Description: This is a digitally signed message part
Autostart not working for me in 5.5.8 version
Hi, Please help to set up the autostart of mysql when the Linux server starts. It is not working for me after installing to version 5.5.8. I have been using different versions of mysql for quite some time with different servers, Fedora versions. All these are working for autostart. But for this 5.5.8 I tried on two servers and both are not working for autostart. Please help. The following are my details:=- Installed on Fedora 12 Linux Previously mysql 5.1.48 is working and autorestart is also working. Now installed 5.5.8 Using manual starting is working /usr/local/mysql/bin/mysqld_safe But the auto start is not working. I have done this $ cp /usr/local/mysql/bin/support-files/mysql.server /etc/init.d/mysql $ chmod +x /etc/init.d/mysql $ ln –s /etc/init.d/mysql /etc/rc3.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc5.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc0.d/K01mysql thanks and rgds, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Autostart not working for me in 5.5.8 version
Hi, I will answer my own question. I have to add a line in (/etc/my.cnf) as follows:- basedir=/usr/local/mysql I have installed mysql in /usr/local/mysql. But the same was done in previous versions and I do not need to add this. Anyway, now that it is working. rgds, --- On Thu, 12/16/10, Yangontha Maung yangontha5...@yahoo.com wrote: From: Yangontha Maung yangontha5...@yahoo.com Subject: Autostart not working for me in 5.5.8 version To: mysql@lists.mysql.com Date: Thursday, December 16, 2010, 11:14 AM Hi, Please help to set up the autostart of mysql when the Linux server starts. It is not working for me after installing to version 5.5.8. I have been using different versions of mysql for quite some time with different servers, Fedora versions. All these are working for autostart. But for this 5.5.8 I tried on two servers and both are not working for autostart. Please help. The following are my details:=- Installed on Fedora 12 Linux Previously mysql 5.1.48 is working and autorestart is also working. Now installed 5.5.8 Using manual starting is working /usr/local/mysql/bin/mysqld_safe But the auto start is not working. I have done this $ cp /usr/local/mysql/bin/support-files/mysql.server /etc/init.d/mysql $ chmod +x /etc/init.d/mysql $ ln –s /etc/init.d/mysql /etc/rc3.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc5.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc0.d/K01mysql thanks and rgds, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=yangontha5...@yahoo.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: Bulk Insertion Performance
Hi Mark, On Thu, Dec 16, 2010 at 4:50 AM, Mark Matthews mark.matth...@oracle.com wrote: Feris, I don't know what Kettle is doing under the hood, but if it's doing addBatch(), executeBatch(), then adding rewriteBatchedStatements=true to your MySQL JDBC URL should probably help quite a bit. It works. By having rewriteBatchedStatements=true in the jdbc url it increases. Now it performs an average 4500 rows / second. Thanks Mark. Regards, Feris
