Translation of summary of last part, "Techniques, used for debugging of Production applications" just published. This is almost end, only appendix about backup techniques and epilogue left.

Summary.

In the last chapter we discussed methods of testing problems which can happen only on production server. Lets repeat them:

Method #25: if something unexpected happens check error log first.


Method #26: turn InnoDB Monitor to on to have information about all InnoDB transactions in the error log file.


Method #27: use slow query log to find all slow queries.


Method #28: use MySQL Sandbox for fast and convenient testing of your application using several versions of MySQL server.


Method #29: use part of data when work with …

Translation of summary of last part, "Techniques, used for debugging of Production applications" just published. This is almost end, only appendix about backup techniques and epilogue left.

Summary.

In the last chapter we discussed methods of testing problems which can happen only on production server. Lets repeat them:

Method #25: if something unexpected happens check error log first.


Method #26: turn InnoDB Monitor to on to have information about all InnoDB transactions in the error log file.


Method #27: use slow query log to find all slow queries.


Method #28: use MySQL Sandbox for fast and convenient testing of your application using several versions of MySQL server.


Method #29: use part of data when work with …

Let’s suppose that your backup process looks like this: you stop a replication replica, shut down MySQL, and copy away the data directory. Assume that the replica is perfect and has the same data as the master. Nothing is broken, nothing is wrong, everything is working fine. In most cases, this should work, right? Under what kinds of circumstances will you not get all your data back if you restore the file copy and start MySQL?

I've been gathering some interesting and useful information when dealing with Pentaho Reporting, Pentaho Metadata and characters not represented in the standard ASCII character set. This bucket of tips will make it into our documentation ASAP, but I thought it prudent to share it with our community even sooner.

IMPORTANT CAVEAT: Note that where I specify UTF-8, I am only doing that as a reference encoding... the encoding I speak of in most cases can represent any extended character set; UTF-8 is a common one for multi-national apps, because it represents multi-national characters.

Character encoding is key to displaying multi-byte or special characters from character sets outside of the standard ASCII character set. Any text-based files that contain special characters in their glyph form must be encoded as at least UTF-8, or in the character encoding for the language you are attempting to display.

The …

Please join us on Tuesday, Sept. 28 for an afternoon of networking and educational opportunities as the IOUG hosts Matt Yonkovit, MySQL expert, for his presentation “MySQL: What You May or May Not Know.”

Tuesday, September 28 | 1:00 p.m. – 5:00 p.m.

Agenda:

1:00 p.m. – 2:00 p.m.
The 5 Minute DBA: A Crash Course to MySQL DBA Troubleshooting and Optimizations

Many people who are charged with running MySQL are not DBAs, rather they are developers, system administrators, network administrators, etc. Typically these people put on a DBA hat only when there is a problem to solve or to deal directly with. These people are called “the 5 minute DBAs,” dealing with databases issues for only a very short time in any given week. This session will give these 5 minute warriors some basic tools and skills in …

The register put up an article on MYSQL'S NON-HEROIC FUTURE RUNS CASTLE ORACLE.

Lets have a poll about it!

1) Eucalyptus will need to be sold to someone eventually, Oracle would be a great buyer to coddle up too.

2) Marten is there is that it is good publicity to be on stage in front of Oracle customers for Eucalyptus.

3) Publicly siding with Oracle is an awesome way to stick it to Monty.

My bet is a combination of all three, with an order of 1,3,2.

Please leave comments, it turns out that LJ's poll system wasn't allowing anonymous posts.

Internally MySQL uses various methods to manage (or, block) concurrent access to shared structures within the server - the most common being mutexes (or Mutual Exclusion locks), RW Locks, or Semaphores. Each have slightly different properties on how different threads are allowed to interact when trying to access these synchronization points.

There has been much written on the various hot spots in the server around these locking/blocking constructs over the past couple of years, so I won’t go further in to that here. See the excellent blogs from Mikael or Dimitri from within …

Thank you Chennai, for making OSI Days 2010 one of the most memorable events we have been a part of. The three days were a blend of pure open source awesomeness with loads of fun along with serious discussions focusing on technology and how it can be deployed to solve real business problems.

As the Organizing Partner of the conference, we were really concerned about the quality of the sessions at the conference. We had done the first part correct - bring together a stellar team of internationally renowned speakers (something we really had to sweat for!). The other part was to ensure that the participants are able to get the best out of the sessions. We hit some glitches, but all-in-all we did a decent job. Lessons have been learned, next edition will be grander and more accessible than this one.

…

Thank you Chennai, for making OSI Days 2010 one of the most memorable events we have been a part of. The three days were a blend of pure open source awesomeness with loads of fun along with serious discussions focusing on technology and how it can be deployed to solve real business problems.

As the Organizing Partner of the conference, we were really concerned about the quality of the sessions at the conference. We had done the first part correct - bring together a stellar team of internationally renowned speakers (something we really had to sweat for!). The other part was to ensure that the participants are able to get the best out of the sessions. We hit some glitches, but all-in-all we did a decent job. Lessons have been learned, next edition will be grander and more accessible than this one.

…

I wrote couple of weeks ago on dangers of bad cache design. Today I’ve been troubleshooting the production down case which had fair amount of issues related to how cache was used.

The deal was as following. The update to the codebase was performed and it caused performance issues, so it was rolled back but yet the problem remained. This is a very common case when you would see customer telling you everything is the same as it was yesterday… but it does not work today.

When I hear these words I like to tell people computers are state machines and they work in predictable way. If it does not work same today as it worked yesterday something was changed… it is just you may not recognize WHAT was changed. It may be something subtle as change in query plan or increase in search engine bot activity. It may be RAID writeback cache disabled …