I used Ubuntu 12.04 LTS on Amazon EC2 to download, compile, and install Varnish cache.

As of this writing, you can find the latest stable release at https://www.varnish-cache.org/releases

One of the decisions I notice acutely about other companies’ products is their user model. I always notice it, and it makes me either smile or grit my teeth. Companies get this wrong all the time.

• Right: a user account owns itself and is affiliated to a company/organization/etc. It may belong to teams and have various levels of permissions. But the person who created the account owns the account.
• Wrong: a user account is created and owned by, and depends on, an organization or company.

The difference may seem silly. Why would anyone care?

Think of GitHub. You probably have your own opensource repos, and you probably participate in your company’s repos. You probably also participate in some teams for repos that you care about, which are owned by other organizations or users. You can do this all with a single account.

What if …

We recently added a token-based authentication example to the Siesta repository that provides an excellent starting point for building authenticated APIs using our lightweight HTTP handler library for Go. This example, modeled after our own internal API services, demonstrates features and practices that we’ve developed and found useful after using Siesta in production for many months.

Here’s what you’ll see in this “meaty” example:

• Request identification and logging
• Token-based authentication
• Use of typed URL parameters
• Usage of a handler for some state, such as a database
• JSON responses
• “Pre” and “post” middleware chains
• Error handling and bypassing of handlers …

Recently a friend asked about Installing Percona Monitoring Tools for Nagios as he was facing a few issues. I managed to set-it-up on my ubuntu VM. Sharing the the work-log…

The post Install Percona Monitoring Tools for Nagios – MySQL Plugins first appeared on Change Is Inevitable.

Like any good, thus lazy, engineer I don’t like to start things manually. Creating directories, configuration files, specify paths, ports via command line is too boring. I wrote already how I survive in case when I need to start MySQL server (here). There is also the MySQL Sandbox which can be used for the same purpose.

But what to do if you want to start Percona XtraDB Cluster this way? Fortunately we, at Percona, have engineers who created automation solution for starting PXC. This solution uses Docker. To explore it you need:

1. Clone the pxc-docker repository:
   git clone https://github.com/percona/pxc-docker …

[…] PlanetMySQL Voting: Vote UP / Vote DOWN Full article:MySQL Cluster: Una introducción en Español. […]

MariaDB 5.5.44 was recently released (it is the latest MariaDB 5.5), and is available for download here:

https://downloads.mariadb.org/mariadb/5.5.44/

This is a maintenance release, and no major changes, so there are only several noteworthy items (but one of those being a security fix and five potential crashing bug):

• Security Fix: Client command line option –ssl-verify-server-cert (and MYSQL_OPT_SSL_VERIFY_SERVER_CERT option of the client API) when used together with –ssl will ensure that the established connection is SSL-encrypted and the MariaDB server has a valid certificate. This fixes CVE-2015-3152.
• Crashing Bug: mysql_upgrade crashes the server with REPAIR VIEW ( …

MariaDB 10.1.5 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.1.5/

This is the 3rd beta, and 6th overall, release of MariaDB 10.1. There were not many major changes in this release, but a few notable items, as well as many overall bugs fixed (I counted 306).

Since it’s beta, I’ll only cover the major changes and additions, and omit covering general bug fixes (feel free to browse them all here).

To me, these are the highlights:

• New status variables: New status variables Binlog_group_commit_trigger_count, …

Slave election is a popular HA architecture,  first MySQL MariaDB toolkit to manage switchover and failover in a correct way was introduce by Yoshinori Matsunobu into MHA.

Failover and switchover in asynchronous clusters require caution:

- The CAP theorem need to be satisfy. Getting strong consistency, require the slave election to reject transactions ending up in the old master when electing the candidate master.

- Slave election need to take care that all events on the old master are applied to the candidate master before switching roles.

- Should be instrumented to found a good candidate master and make sure it's setup to take the master role.

- Need topology detection, a master role can't be pre defined, as the role …

Setting up environments, starting processes, and monitoring these processes on multiple machines can be time consuming and error prone - stale settings from previous test runs, wrong configurations, wrong commands, package conflicts, etc.. quite a few things can go wrong. If you are using Galera Cluster, you would probably want application developers to have a proper development environment on their local computers. Proper here means testing your code on a local Galera Cluster, not on a single instance MySQL. Galera Cluster differs from a single instance MySQL, so this allows you to catch these differences early in the project. But how can you quickly roll out a mini test clusters to your application developers, without having them waste time setting these up? This is where Vagrant comes in.

Vagrant is a system that allows you to easily create and move development environments from one machine to another. Simply define what type of VM you …