As you've heard, MaxScale was recently released, and we'd love for you to try it out and let us know your thoughts.
Anders Karlsson and Ivan Zoratti have written some excellent posts on downloading and setting it up, so if you're intersted in that, please see their respective posts for quick, detailed instructions.
I have spent some time thinking about and working on a project that went public on GitHub at the beginning of this year. That project is called MaxScale and is primarily a proxy server for MySQL/MariaDB databases, although it can be something much more than this. The obvious and often asked question is why do we need another proxy? I want to try to give you a flavor for what MaxScale is and why I think there is a need for a tool like MaxScale.
The architecture of MaxScale makes it different from your average proxy
Do you want to learn more about the MariaDB Audit-Plugin? Join Ralf Gebhardt on 5.12.2013 for his live webcast: http://www.skysql.com/why-skysql/webinars/mariadb-audit-plugin-overview
Introduction
Drupal is one of the most popular Content Management Systems (CMS) and is used increasingly in high-visibility sites, such as www.whitehouse.gov. This has brought a lot of attention on how to get the most performance out of Drupal and how to improve the availability of such sites. In this blog series I'll take you through the basics and on through to designing your own HA Drupal site.
But first, we need to understand what the challenges are in getting Drupal (or indeed any CMS) working on multiple servers in such a way as to ensure high availability and performance.
Background: SkySQL is a distributed company. Nearly all of us work from home. To be productive, we need to emulate the best aspects of collaborating as if we were working next to one another. Given that nearly all of us had worked under similar distributed conditions at MySQL AB, we knew what we were getting into when we were founded. Obviously, we wanted to learn from our past experiences when making our choices for tools and processes.
This post is about a fairly technical detail of how Galera works. I'm writing it down in preparation for testing this feature so that I can agree with Alex whether to file a bug or not. I'm sharing it on my blog just in case someone else might benefit from learning this.
Galera 2.0 introduces rolling schema upgrades. This is a new way to do non-blocking schema changes in MySQL.
As the name suggests, it is done as a rolling upgrade. Having seen clusters doing rolling upgrades before, I assumed this is what happens:
The slides from last week’s talks I (co-)presented at Percona Live and Linuxcon Europe are now available from our web site.
If you run (or plan to deploy) high availability clusters — with or without DRBD — you might find a new section on our web site handy. Our Technical Guides collection is a compilation of LINBIT expert HA knowledge, which we’re opening up to everyone.
Yes, this also includes PDF versions of the DRBD User’s Guide and the Linux-HA User’s Guide.
More Technical Guides will be added as we go along. LINBIT Cluster Stack support customers will receive new Tech Guides approximately one month before they pop up on …
[Read more]Nagios is a powerful monitoring system and here we will learn how to monitor MySQL through Nagios. We will be installing Nagios, required plugins and configuring it to monitor MySQL…
The post 10 Steps: MySQL Monitoring through Nagios: Install & Configure first appeared on Change Is Inevitable.
Every once in a while, we hear of users with corruption in a file
system that sits on top of DRBD. That may be easy or tricky to
resolve. If you’re lucky, a simple fsck will resolve
the corruption. If you’re not quite that lucky, you may have to
get out your backups.
But that’s typically not DRBD’s fault. Typically not at all, not in the least bit. DRBD is a block device, and as such it has no idea what rests on top of it. It has no concept of a filesystem, let alone its integrity. That of course is true for any other block device as well. If you have, say, RAID-1, and something corrupts the file system on top of it, then of course that corruption will be happily replicated across both component devices. DRBD is no different, except that its component devices are stored across distinct physical nodes.
And even if everything about your filesystem is logically correct, there’s still the chance that a …
[Read more]