MySQL Cluster: El ‘qué’ y el ‘cómo’.
Para aquellos que encuentran mucho sobre MySQL en Inglés pero poco en Español: mi pequeña aportación.
En el enlace tenéis información sobre qué es MySQL Cluster y cómo funciona. Incluso con ejemplos técnicos para romper las barreras y ayudar a simplificarlo (espero).
We’re on the move again. Come and join us on the 7th of November at the Oracle office in Barcelona. Find out more details about what was announced at MySQL Connect, as well as what’s next…
For more information about this event please visit the link below:
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.
From my testing MySQL Cluster on the Raspberry Pi’s I thought I’d share this little extract, just in case someone tries the same, some day.. somewhere.. why? I don’t know.
Ok, so when we pull the plug on one of the pi’s, we have of each component falling down, but because one of them is the arbitrator (node-id=2) then cluster falls over.
Before the ‘accident’:
Ok, so I’ve been playing around with the idea of setting up MySQL cluster on a couple of Raspberry Pi’s and this is how it has been going.
First of all, for anyone else who’s reading this, it’s not a new thing, I know, and I highly recommend reading A.Morgans blog, http://www.clusterdb.com/mysql-cluster/mysql-cluster-running-on-raspberry-pi/ as well as someone else’s blog: http://markswarbrick.wordpress.com/, cheers Mark.