MySQL QA Episode 8: Reducing Testcases for Engineers: tuning reducer.sh

Welcome to MySQL QA Episode 8: Reducing Testcases for Engineers: tuning reducer.sh Advanced configurable variables & their default/vanilla reducer.sh settings FORCE_SKIPV FORCE_SPORADIC TIMEOUT_COMMAND & TIMEOUT_CHECK MULTI_THREADS MULTI_THREADS_INCREASE QUERYTIMEOUT STAGE1_LINES SKIPSTAGE FORCE_KILL Some examples FORCE_SKIPV/FORCE_SPORADIC TIMEOUT_COMMAND/TIMEOUT_CHECK Full-screen viewing @ 720p resolution recommended.

MySQL QA Episode 6: Analyzing and Filtering

Welcome to MySQL QA Episode #6! Today we will look into analyzing and filtering our QA run. We’ll use tools like pquery-prep-red.sh, pquery-clean-known.sh & pquery-results.sh 1. Quick re-cap and QA run setup 2. pquery-prep-red.sh 3. pquery-clean-known.sh 4. pquery-results.sh 5. Bonus: pquery reach – pquery-reach++.sh We’ll also introduce the text_string.sh tool which extracts a most-specific text string […]

MySQL QA Episode 5: Preparing Your QA Run with pquery

Welcome to MySQL QA Episode #5! In this episode we’ll be setting up and running pquery for the first time… and I’ll also trigger some actual bugs (fun guaranteed)! I’ll also introduce you to mtr_to_sql.sh and pquery-run.sh. pquery-run.sh (the main wrapper around pquery) is capable of generating 80-120 MySQL Server crashes – per hour! See how […]

MySQL QA Episode 4: QA Framework Setup Time!

Welcome to MySQL QA Episode 4! In this episode we’ll look into setting up our QA Framework: percona-qa, pquery, reducer & more. 1. All about percona-qa 2. pquery

3. reducer.sh

4. Short introduction to pquery framework tools The tools introduced in this episode will be covered further in next two episodes. Full-screen viewing @ […]

Choosing a MySQL HA Solution – Post-Webinar Q&A

Thanks to everyone who was in attendance on 05 June 2013 for my “Choosing a MySQL HA Solution” webinar. If you weren’t able to make it but are interested in listening to the presentation, it’s currently up and available for viewing over at percona.com. My apologies if we weren’t able to get to your question […]