MySQL QA

MySQL QA
Just a blog to leave comments about and suggestion of QA of MySQL, MySQL Cluster and MySQL Replication software.

Comments

Post a Comment

Popular posts from this blog

MySQL Cluster Replication

MySQL QA In the 5.1 release MySQL Cluster will support replication to another MySQL installation. The replication is handled using Row Bases Replication instead of Statement Based Replication. I have been testing it for about a year now and it has gotten really hard for me to break at this point, but I am still trying. So what is so cool about Cluster Replication? Good question! One answer: Cluster Replication really gives a company five 9's (99.999%) in up time. You can have a Master Cluster in the main site supporting the business and have another Slave Cluster in a total different site that can be used as a backup for times there are issues with main site. In addition, the Slave Cluster can also be used for reporting or data mining to take that traffic off of the main Cluster. How hard is it to setup? Another great question. Answer: Easy So to set it up, you would create two set of Clusters configured the way that you wanted them. You configure the Master MySQLD to create a bin ...
Read more

New MySQL System QA blog

Hi, It has been a while since I last posted, but I wanted to post about my teams NEW blog page. New System QA Blog As always, we look for ways to improve QA and your feedback is always welcomed. Best Wishes, /Jeb
Read more

Under Construction: Building the MariaDB Benchmarking Test Automation Framework (TAF)

Image
Building a New Test Automation Framework for MariaDB MariaDB has given me the chance to pursue a lifelong dream: creating a new Test Automation Framework (TAF) — an improved, expanded evolution of the Autobench3 framework I originally built for MySQL. Autobench3 was never just a benchmark API. It was a framework that wrapped benchmark APIs to provide a consistent platform for configuration and abstraction. Instead of requiring deep knowledge of each benchmark tool, Autobench3 allowed developers to work with simple command‑line options and property files. The framework made clear what suite was being run, what test case was in play, which database software was targeted, and what overrides were applied. When running, the framework would load the chosen test suite into itself — becoming Sysbench, becoming DBT2 — and then drive the workload through a consistent set of lifecycle stages. Autobench3: Still in Service, But Limited Autobench3 continues to serve MySQL well in worklog d...
Read more