MySQL Workbench 5.2.40 GA Released
The MySQL Developer Tools team is announcing the next maintenance release of it’s flagship product, MySQL Workbench, version 5.2.40.
This version contains more than 28 bug fixes applied over version 5.2.39.
MySQL Workbench 5.2 GA
• Data Modeling
• Query
• Administration
Please get your copy from our Download site.
Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.
http://dev.mysql.com/downloads/workbench/
Workbench Documentation can be found here.
http://dev.mysql.com/doc/workbench/en/index.html
Utilities Documentation can be found here.
http://dev.mysql.com/doc/workbench/en/mysql-utilities.html
In addition to the new Query/SQL Development and Administration
modules, version 5.2 features improved stability and performance –
especially in Windows, where OpenGL support has been enhanced and the UI
was optimized to offer better responsiveness.
This release also includes improvements to the scripting capabilities of the SQL Editor. You can read more about it in
http://wb.mysql.com/workbench/doc/
For a detailed list of resolved issues, see the change log.
http://dev.mysql.com/doc/workbench/en/wb-change-history.html
If you need any additional info or help please get in touch with us.
Post in our forums or leave comments on our blog pages.
- The MySQL Workbench Team
Article source: https://blogs.oracle.com/mysqlworkbench/entry/mysql_workbench_5_2_40
Some throttling for PECL/mysqlnd_ms 1.4
Users of MySQL Replication sometimes throttle client requests to give slaves time to catch up to the master. PECL/mysqlnd_ms 1.4, the current development version, features some throttling through the quality-of-service filter and global transaction identifier (GTID). Both the plugins client-side GTID emulation and the MySQL 5.6 built-in GTID feature can be used to slow down PHP MySQL requests, if wanted.
How its done
The replication plugin has a neat feature called quality-of-service filter. If, for example, the quality of service you need from a MySQL Replication cluster is “read your writes”, you call mysqlnd_ms_set_qos($connection, MYSQLND_MS_QOS_CONSISTENCY_SESSION). This instructs the plugin to either use a master or a slave, that has replicated your writes already, for all further reads. The plugin takes care of picking an appropriate cluster node. Once you are done with “read your writes” you can relax the service quality to make node selection faster.
By default, MYSQLND_MS_QOS_CONSISTENCY_SESSION will enforce reading from the master. This is undesired as it increases the load on the master. However, before the introduction of global transaction identifiers, there was no safe way of knowing whether a slave had replicated a certain update already or not.
Using either the plugins GTID emulation or the MySQL 5.6 build-in GTID feature, one can reliably check the up-to-date status of a slave using a SQL SELECT statement. GTIDs are some kind of unique transaction sequence numbers. If you know the transaction sequence number of a write operation, you can check whether it has been replicated using a statement like, for example, SELECT GTID_SUBSET('gtid_of_write', @@GLOBAL.GTID_DONE) AS trx_id FROM DUAL. Please, check my previous posts for a more precise description of the GTID feature. This statement will check the replication status and return immediately.
SQL_THREAD_WAIT_AFTER_GTIDS(string gtids [, timeout])
Alternatively, a MySQL 5.6 user can issue SELECT SQL_THREAD_WAIT_AFTER_GTIDS('gtid_of_write') which will block until either the slave has replicated the write in question or the statement times out. This is great to throttle clients and prevent them to send new updates before the slaves have caught up. This is what some throttling is about. You can control which logic PECL/mysqlnd_ms shall use when searching for an up-to-date slave.
Strictly speaking, you could do it in 1.3 already, if using MySQL 5.6, which is not GA yet. GTIDs are opaque to the plugin. The configuration contains a SQL statement to fetch gtid_of_write and one to check if gtid_of_write has been replicated already. You have been free to either use SQL_THREAD_WAIT_AFTER_GTIDS or not for those config settings.
The new bit
New is a wait_for_gtid_timeout setting that can be used with the GTID emulation. If wait_for_gtid_timeout is set, the plugin will poll a slaves state for wait_for_gtid_timeout seconds regardless of the SQL statement configured. The plugin first runs the SQL statement to check if gtid_of_write has been replicated already. If not, it checks if there is time left for another poll attempt, sleeps for second and polls the status again.
All this is done transparently in the background. All the application does is formulate its quality of service needs.
Throttling makes synchronization costs visible
Throttling client requests should not be understood as a hack. MySQL Replication happens to be a lazy primary copy system. All updates must be performed on the primary (master). Synchronization of secondaries (slaves) is lazy. Update transactions are finished once the primary has finished them. An update transaction never waits for secondaries to catch up. This is an easy to implement, often fast and simple approach.
The drawbacks are temporarily stale data on the secondaries and limited gains in availability over a single server.
Clients get confirmation for update transactions as soon as they are finished on the primary. As soon as they are saved on just one server. There is no guarantee that the transaction ever makes it to a secondary. In the unlikely worst case, the primary crashes in an unrecoverable manner and transactions are lost before being replicated. Thus, little gain over a single server. If you don’t want that, you need eager synchronization. This is what MySQL Cluster offers, if you want it. For eager synchronization one needs to slow down updates and wait for one or all replicas to confirm the update. If updating one secondary is all you need, go for MySQL Semisynchronous Replication.
It may not be technically valid comparison, however, the slow down and wait reminds me of throttling. MySQL lets you choose whether you want to do the wait on demand and on the client side (MySQL Replication: lazy synchronization) or built-in to the distributed system (MySQL Cluster: eager synchronization). Putting all this in a matrix shows the wide range of database replication options that MySQL has to offer.
Happy hacking!
Veröffentlicht am
Tuesday, May 15th, 2012 at 2:11 pm in PlanetMySQL (english), PlanetPHP (english).
Ein RSS 2.0 feed ist verfügbar.
Es ist möglich eine Antwort zu verfassen oder den
Eintrag per Trackback zu verlinken.
Article source: http://blog.ulf-wendel.de/2012/some-throttling-for-peclmysqlnd_ms-14/
Sophos Offers Partners New Complete Security Suites To Meet Clients’ Changing Needs
In response to partner and customer demand, Sophos today introduced new Complete Security Suites; Web Protection, Data Protection and Complete Security. These suites offer Sophos partners the tools they need to help their clients address the evolving security challenges IT departments are facing due the consumerization of IT, the rise of advanced persistent threats, and an increase in malware.
“The evolution of Sophos technology and the new ‘Complete Security Suites’ represent a clear and forward-looking vision to manage the advanced multi-vectored threats businesses face,� said Robert Newburn, head of Information Security and Managed Services, Trustmarque. “Security never stands still and neither does Sophos. Through significant in-house development and tactical acquisitions they have built a compelling set of integrated technologies simplifying security management, driving down administration costs and offering customers a mature set of proven tools to protect the endpoint, mobile devices and Gateway.�
The Complete Security Suites combine key functions like endpoint, data and web and email protection, along with mobile device management and protection for Microsoft Exchange and SharePoint. The new offerings give partners a competitive edge in the industry—one vendor, one license, ease of management and deployment. And the array of market-leading solutions creates even more secure environments for their clients at a greater value.
“As a managed service provider, we are our clients’ IT departments, so keeping management costs down is critical to our business,� said Marcus Bearden, vice president of technology, Carceron “The centralized management of Sophos’ Complete Security Suites will reduce our administrative costs, thus reducing costs for our customers—a true win-win. Additionally, they will allow us to offer our clients a better value than an a la carte model while satisfying all their security needs.�
The Complete Security Suites will also shorten the sales cycle for Sophos partners as clients no longer have to evaluate individual solutions in order to solve each security challenge. Instead, they are able to offer solutions that work together—across all points—from a trusted provider.
“Our clients face an ever-changing variety of new security challenges. Since IT managers are already tasked with accomplishing more while using less resources, we need to provide solutions that quickly address all the different aspects of IT security,� said Stephen Merritt, software partner manager, SHI International. “Evaluating multiple security solutions is time consuming for both us and our customers, so the ability to present a single, dynamic and scalable bundle that meets all a customer’s security needs helps keep their focus on other initiatives within an environment they are confident is secure.�
“We recognize that partners are operating in a competitive environment, so they need tools that will help them meet their clients’ demands for stronger security systems,â€� said John Shaw, vice president product management Sophos. “We have built this complete security system for IT because IT teams shouldn’t have to spend time determining which of their point security products is at fault every time they have a problem, only to find that the problem is that the point products don’t work together. With our suites, customers know it’s always Sophos securing them, and they can be confident that they will be backed by both our industry-leading support and our excellent partners.â€�
For additional information on the new Complete Security Suites, please visit: http://www.sophos.com/en-us/products/complete.aspx.
Announcing the Explain Analyzer
The explain statement can be an important tool for understanding how a query is being executed and what you can do to make it run better. Although the output of EXPLAIN is relatively straightforward it can be confusing to inexperienced users or can be mangled by terminal wrapping.
To help with these problems as well as provide a pastebin for MariaDB developers to share explains during development we created The MariaDB/MySQL Explain Analyzer. This tool:
- Helps unmangle explains (both vertical and tabular format)
- Displays explains in an easy-to-read format.
- Highlights and provides explanations for some terms.
- Links to KB articles for different optimization techniques.
- (Optionally) Allows you to save the explain for sharing.
This is the first release so there are still improvements to make. If you have any suggestions, feature requests or bug reports please let us know.
For more information, please see this KB article.
Article source: http://blog.montyprogram.com/announcing-the-explain-analyzer/