For those of you in around Sao Paulo this week, Aiton Lastori send me the following:
Next week we will host a MySQL Happy Hour at Oracle's Sao Paulo office.
We are exited because there are room for 100 people and over 500
subscribed! Oracle marketin provided the money for the free beer and Ana, our lead dev in Brazil, and is doing an amazing job organizing
everything. I've created a group in meetup.com http://www.meetup.com/MySQL-BR/.
I’ll be presenting at Oracle Open World on the causes of downtime in MySQL, and how to prevent it. This is a research-based session that presents an easy-to-digest post-mortem of hundreds of emergency issues filed by Percona customers. The real causes and types of downtime surprised me quite a bit, and the preventions run counter to a lot of conventional wisdom. I’ll just give a preview by saying that you should consider it a top priority to monitor how full your disks are!
If you’re going to Surge, which you should, you need to book your hotel now, or you’ll lose the conference discount. It’s a nice hotel and a great discount. It also supports the conference if you book this hotel — conference venues typically put a requirement in the contract that they must sell X number of rooms for the conference, or the organizer has to pay a penalty.
Have just read MySQL Global status difference using MySQL procedures / functions, by Andres Karlsson. Have commented, but realized I did not provide with a direct answer. In the comment, I suggested checking out a solution based on views, found in common_schema.
MySQL will be big at Oracle Open World. Not only are their demo pods, a community run area, and two community organized tracks on the first day! A full MySQL session track will be part of Open World for the first time. A full searchable list of all session with the options is available here a quick list of MySQL sessions is below. Note the sessions starting with IOUG are on Community Sunday on October 2nd.
If you love a software product, you should try to improve it, and not be afraid of criticizing it. This principle has guided me with MySQL (where I have submitted many usability bugs, and discussed interface with developers for years), and it proves true for Tungsten Replicator as well. When I started working at Continuent, while I was impressed by the technology, I found the installation procedure and the product logs quite discouraging. I would almost say disturbing.
Flash devices are described in part by their write amplification factor (or WAF). When the OS writes a page once the device might write it more than once and this multiple is the write amplification factor. The WAF isn't always described in marketing and even if it were the value you get in production is workload dependent.
With the fast growth of virtualized data centers, and companies like Google, Amazon and Facebook, it's easy to forget how much is built on open-source components, aka commodity software. In a very real way open-source has enabled the huge explosion of commodity hardware, the fast growth of the internet itself, and now the further acceleration through cloud services, cloud infrastructure, and virtualization of data centers.
If you use InnoDB and have long-running select statements then the InnoDB undo space can grow large because purge can't advance beyond the longest open transaction. If this is blocked for too-long then pages to be purged might leave the InnoDB buffer cache and the purge thread will have to do many disk reads. As the InnoDB purge process is single-threaded it might not be able to catch up and a server can use too much disk space for a very long time.