Many users are challenged with how to setup multi-master, multi-site MySQL clusters. How to do you go from a single database server to a scalable cluster? Or move from a brittle MySQL replication system to a transparent, manageable database cluster? In this joint webinar with Continuent, Percona examines how Continuent Tungsten addresses these problems.
First, we discuss the read-write
December 5, 2013 By Severalnines
Thanks to everyone who attended yesterday’s webinar; if you missed the sessions or would like to watch the webinar again & browse through the slides, they are now available online.
Thanks again to our speaker, Seppo Jaakola from Codership, the creators of Galera Cluster, for this in-depth talk on Galera Cluster Best Practices - Zero Downtime Schema Changes.
Webinar topics covered
The binary and source versions of MySQL Cluster 7.3.3 have now been made available at http://www.mysql.com/downloads/cluster/.
A description of all of the changes (fixes) that have gone into MySQL Cluster 7.3.3 (compared to 7.3.2) is available from the 7.3.3 Change log.
The binary version for MySQL Cluster 7.2.14 has now been made available at http://www.mysql.com/downloads/cluster/.
A description of all of the changes (fixes) that have gone into MySQL Cluster 7.2.14 (compared to 7.2.13) is available from the 7.2.14 Change log.
The binary and source versions of MySQL Cluster 7.1.29 have now been made available at http://www.mysql.com/downloads/cluster/.
A description of all of the changes (fixes) that have gone into MySQL Cluster 7.1.29 (compared to 7.1.28) is available from the 7.1.29 Change log.
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:
http://www.oracle.com/us/dm/29173-emeafm13045970mpp010-oem-2020763-es.html
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:
http://www.oracle.com/us/dm/29173-emeafm13045970mpp010-oem-2020763-es.html
On Thursday 12th September I co-presented a webinar on how MySQL Cluster delivers the key benefits of NoSQL Data Stores without having to give up the features that people rely on from relational databases (consistency, SQL etc.). There was a particular focus on how to use the new node.js JavaScript API which was recently released as part of MySQL Cluster 7.3. If you weren’t able to attend the live event then the webinar replay is available here. If you scroll down to the bottom of this post you’ll see a summary of the Questions and Answers from the session.
The new MySQL JavaScript Connector for Node.js is designed to deliver simplicity and high performance for JavaScript users.
Enables end-to-end JavaScript development, from the …
[Read more]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,$ …
