By going to the download section of  SkySQL website  some users have noticed “MariaDB Audit Plugin”. This auditing feature for MySQL has been requested by more and more customers. Legal constraints make it mandatory for more and more companies to keep logging information about database access and activity.

It is very important for the MySQL [...]

So, now I’ve got my Raspberry Pi’s tested, and running MySQL Cluster we’ll need some form of checking it’s up and running, as with the rest of our MySQL servers.

Monitoring via a Remote Agent

First issue, of course, is that, with my existing MEM console, I have no need to re-install MEM, but rather want to deploy an agent so that I can monitor the MySQL Cluster.
This poses it’s first problem, as there isn’t an ARM-ready agent software available. Remember, it’s not a supported platform. So what can we do? Setup a remote Enterprise Monitor agent, so that, we can monitor the MySQL Cluster, albeit at the sacrifice of not having the agent local on each Raspberry Pi, and hence, not be able to capture the o.s. data.

Config change

So, on my Ubuntu server, I go to the agent install directory:

  cd /opt/mysql/enterprise/agent/etc
  vi mysql-mypi01-agent.ini
  :1,$ …

So, now I’ve got my Raspberry Pi’s tested, and running MySQL Cluster we’ll need some form of checking it’s up and running, as with the rest of our MySQL servers.

Monitoring via a Remote Agent

First issue, of course, is that, with my existing MEM console, I have no need to re-install MEM, but rather want to deploy an agent so that I can monitor the MySQL Cluster.
This poses it’s first problem, as there isn’t an ARM-ready agent software available. Remember, it’s not a supported platform. So what can we do? Setup a remote Enterprise Monitor agent, so that, we can monitor the MySQL Cluster, albeit at the sacrifice of not having the agent local on each Raspberry Pi, and hence, not be able to capture the o.s. data.

Config change

So, on my Ubuntu server, I go to the agent install directory:

  cd /opt/mysql/enterprise/agent/etc
  vi mysql-mypi01-agent.ini
  :1,$ …

So, now I've got my Raspberry Pi's tested, and running MySQL Cluster we'll need some form of checking it's up and running, as with the rest of our MySQL servers.

Monitoring via a Remote Agent First issue, of course, is that, with my existing MEM console, I have no need to re-install MEM, but rather want to deploy an agent so that I can monitor the MySQL Cluster. This poses it's first problem,

I was rooting through past blog entries and I stumbled accross a draft post on setting up multi-master (update anywhere) asynchronous replication for MySQL Cluster. The post never quite got finished and published and while the material is now 4 years old it may still be helpfull to some and so I’m posting it now. Note that a lot has happened with MySQL Cluster in the last 4 years and in this area, the most notable change has been the Enhanced conflict resolution with MySQL Cluster active-active replication feature introduced in MySQL Cluster 7.2 and if you’re only dealing with a pair of Clusters, that’s your best option as it removed the need for you to maintain the timestamp columns and backs out entire transactions rather than just the conflicting rows. So when would you use this “legacy” method? The main use case is when you want conflict detection/resolution among a ring of more than …

Connector/Python v1.1.1 is available for testing. It’s the second of a series of alpha releases which will bring some new features. Check out the Change History if you want to keep up with what is being added and changed.

Notable changes for v1.1.1:

• Connection Pooling is now available
• A backend for Django is now (again) provided with Connector/Python.

Connector/Python v1.1.1 is alpha and although in good shape, it’s advised not to use it in production just yet.

Some …

We had an absolutely rocking July this year when we inducted new college graduates (NCGs) into the MySQL team at Oracle, Bangalore.
There were fun themes and games that went hand-in-hand with the training program bringing about a vibrant atmosphere that gave the NCGs a chance to prove that they are indeed a great addition to this high energy MySQL team here in Bangalore :).
The fun part of the induction spanned five Tuesdays and culminated with the grand finale in which we were bowled over by some brilliant performances by the NCGs. What I loved about these Tuesdays was that it jump started the induction programme bringing about some great team building and a very informal introduction to our MySQL team.
On the first Tuesday, the NCGs who were expecting a conventional welcome party were in for a surprise as they were asked to put up an impromptu talent show. After the initial inhibitions and reluctance, they came out with …

This post focuses on the problem of the InnoDB log sequence number being in the future.

Preface: What is an InnoDB log sequence number?

The Log sequence number (LSN) is an important database parameter used by InnoDB in many places.
The most important use is for crash recovery and buffer pool purge control.

Internally, the InnoDB LSN counter never goes backward.
And, when InnoDB writes 50 bytes to the redo logs, the LSN increases by 50 bytes.
As such we can count LSN in megabytes, gigabytes and etc.

Now for the problem: LSN being in the future!

When you have set innodb_force_recovery like this:

innodb_force_recovery=6

and then issue a data affecting query.

For example, if you are dropping a corrupted table after doing a mysqldump for backup …

Tuesday, 10 September 2013Author: colincharles

The MariaDB Server has a long history that is worth chronicling. It began life humbly as just another storage engine. While many were concerned when InnoBase, the makers of InnoDB were acquired by Oracle, MySQL AB still had a plan: acquire Netfrastructure, makers of the now defunct Falcon storage engine and allow Michael “Monty” Widenius to assemble a high calibre team of his choice to create a new transactional storage engine called Maria. Both teams worked even through the Sun acquisition, however Monty decided that MySQL 5.1 was released with much too many bugs that he wanted fixed. It didn’t take long to cement the decision that Monty would leave Sun Microsystems because barely two months passed and Oracle had proposed the acquisition of Sun Microsystems, thus gobbling up the MySQL team too!

Monty looking for a drinking partner in Lisbon

…

The next meetup for the MySQL User Group NL is on September 12

Details and signup: http://www.meetup.com/MySQL-User-Group-NL/events/97461512/