MySQL Enterprise Backup 3.11.1 has been released
Dear MySQL users, MySQL Enterprise Backup v3.11.1, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 3.11.1 is given below. Changes in MySQL Enterprise Backup 3.11.1 (2014-11-05) Bugs Fixed * The copying of the relay log files from a MySQL slave server into a backup (which has been the default behavior of MySQL Enterprise Backup since 3.11.0) crashed MySQL Enterprise Backup when the server is of version 5.5. (Bug #19904912) * The copying of the binary log files from the server into a backup (which has been the default behavior of MySQL Enterprise Backup since 3.11.0) caused some databases to be silently skipped over during the backup process when (1) the binary log files are located in the server's data directory, and the name of any database matches the data directory's base name or (2) the binary log files are located in a subdirectory of the data directory. (Bug #19883801) You can also find more information on the contents of this release in the change log: http://dev.mysql.com/doc/mysql-enterprise-backup/3.11/en/meb-news.html The complete manual for MEB 3.11.1 is at, http://dev.mysql.com/doc/mysql-enterprise-backup/3.11/en/index.html The tool is available for download from Oracle Software Delivery Cloud (http://edelivery.oracle.com/). You can also download the binaries from MOS, https://support.oracle.com Choose the Patches Updates tab, and then use the Product or Family (Advanced Search) feature. If you haven't looked at MEB recently, please do so now and let us know how MEB works for you. Your feedback is greatly appreciated! Please report any problems you have at https://bug.oraclecorp.com/ for the product MySQL Enterprise Backup Thanks, The MySQL build team at Oracle -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Fwd: MySQL 5.5 Slow performance after slave server fail
Hi, I have two servers Mysql 5.5 with master to master replication. The second server failed and I needed to remove it to repair the operating system. After this incident the application users have been notice that the application response have been very slow. Both servers have RAID 1 (mirroring) managed by operating system. Could you help me to understand what's happening? Follow the innodb status: mysql show engine innodb status \G *** 1. row *** Type: InnoDB Name: Status: = 141105 17:43:07 INNODB MONITOR OUTPUT = Per second averages calculated from the last 36 seconds - BACKGROUND THREAD - srv_master_thread loops: 4704 1_second, 4703 sleeps, 470 10_second, 2 background, 2 flush srv_master_thread log flush and writes: 4740 -- SEMAPHORES -- OS WAIT ARRAY INFO: reservation count 194, signal count 201 Mutex spin waits 280, rounds 819, OS waits 9 RW-shared spins 82, rounds 2324, OS waits 74 RW-excl spins 8, rounds 3533, OS waits 110 Spin rounds per wait: 2.92 mutex, 28.34 RW-shared, 441.62 RW-excl TRANSACTIONS Trx id counter 82EC Purge done for trx's n:o 7A75 undo n:o 0 History list length 32 LIST OF TRANSACTIONS FOR EACH SESSION: ---TRANSACTION 0, not started MySQL thread id 301, OS thread handle 0x7ff94db71700, query id 32201 localhost root show engine innodb status ---TRANSACTION 80D6, not started MySQL thread id 41, OS thread handle 0x7ff94dba2700, query id 29440 localhost 127.0.0.1 root ---TRANSACTION 82EB, not started MySQL thread id 40, OS thread handle 0x7ff94dbd3700, query id 32200 localhost 127.0.0.1 root FILE I/O I/O thread 0 state: waiting for i/o request (insert buffer thread) I/O thread 1 state: waiting for i/o request (log thread) I/O thread 2 state: waiting for i/o request (read thread) I/O thread 3 state: waiting for i/o request (read thread) I/O thread 4 state: waiting for i/o request (read thread) I/O thread 5 state: waiting for i/o request (read thread) I/O thread 6 state: waiting for i/o request (write thread) I/O thread 7 state: waiting for i/o request (write thread) I/O thread 8 state: waiting for i/o request (write thread) I/O thread 9 state: waiting for i/o request (write thread) Pending normal aio reads: 0 [0, 0, 0, 0] , aio writes: 0 [0, 0, 0, 0] , ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0 Pending flushes (fsync) log: 0; buffer pool: 0 19995 OS file reads, 12493 OS file writes, 8901 OS fsyncs 0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s - INSERT BUFFER AND ADAPTIVE HASH INDEX - Ibuf: size 1, free list len 2140, seg size 2142, 122 merges merged operations: insert 482, delete mark 661, delete 2 discarded operations: insert 0, delete mark 0, delete 0 Hash table size 276707, node heap has 671 buffer(s) 1.06 hash searches/s, 5.28 non-hash searches/s --- LOG --- Log sequence number 4276155092 Log flushed up to 4276155092 Last checkpoint at 4276155092 0 pending log writes, 0 pending chkp writes 8644 log i/o's done, 0.00 log i/o's/second -- BUFFER POOL AND MEMORY -- Total memory allocated 137363456; in additional pool allocated 0 Dictionary memory allocated 2978314 Buffer pool size 8192 Free buffers 0 Database pages 7521 Old database pages 2756 Modified db pages 0 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 13227, not young 0 0.00 youngs/s, 0.00 non-youngs/s Pages read 20400, created 52, written 5785 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 7521, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] -- ROW OPERATIONS -- 0 queries inside InnoDB, 0 queries in queue 1 read views open inside InnoDB Main thread process no. 870, id 140708344538880, state: sleeping Number of rows inserted 4256, updated 8, deleted 3101, read 6737576 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 2.11 reads/s END OF INNODB MONITOR OUTPUT
MySQL Cluster 7.4.2 has been released
Dear MySQL Users, MySQL Cluster 7.4.2 (Milestone Release) is a public milestone release for MySQL Cluster 7.4. MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.4 makes significant advances in performance; operational efficiency (such as enhanced reporting and faster restarts and upgrades) and conflict detection and resolution for active-active replication between MySQL Clusters. MySQL Cluster 7.4.2 DMR can be downloaded from the Development Releases tab at http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. More information on the Development Milestone Release process can be found at http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL Cluster NDB 7.4.2 (5.6.21-ndb-7.4.2 2014-11-05) MySQL Cluster NDB 7.4.2 is a new release of MySQL Cluster, based on MySQL Server 5.6 and including features under development for version 7.4 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.4. MySQL Cluster NDB 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.4, see MySQL Cluster Development in MySQL Cluster NDB 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development-5-6-ndb-7-4.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.21 (see Changes in MySQL 5.6.21 (2014-09-23) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-21.html). Functionality Added or Changed * After adding new data nodes to the configuration file of a MySQL Cluster having many API nodes, but prior to starting any of the data node processes, API nodes tried to connect to these missing data nodes several times per second, placing extra loads on management nodes and the network. To reduce unnecessary traffic caused in this way, it is now possible to control the amount of time that an API node waits between attempts to connect to data nodes which fail to respond; this is implemented in two new API node configuration parameters StartConnectBackoffMaxTime and ConnectBackoffMaxTime. Time elapsed during node connection attempts is not taken into account when applying these parameters, both of which are given in milliseconds with approximately 100 ms resolution. As long as the API node is not connected to any data nodes as described previously, the value of the StartConnectBackoffMaxTime parameter is applied; otherwise, ConnectBackoffMaxTime is used. In a MySQL Cluster with many unstarted data nodes, the values of these parameters can be raised to circumvent connection attempts to data nodes which have not yet begun to function in the cluster, as well as moderate high traffic to management nodes. For more information about the behavior of these parameters, see Defining SQL and Other API Nodes in a MySQL Cluster (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-api-definition.html). (Bug#17257842) Bugs Fixed * Online downgrades to MySQL Cluster NDB 7.3 failed when a MySQL Cluster NDB 7.4 master attempted to request a local checkpoint with 32 fragments from a data node already running NDB 7.3, which supports only 2 fragments for LCPs. Now in such cases, the NDB 7.4 master determines how many fragments the data node can handle before making the request. (Bug#19600834) * The server side of an NDB transporter disconnected an
