Severalnines Blog
The automation and management blog for open source databases

Severalnines blog

Filter by:
Clear
Apply (1) filters
25 blog posts in 12 categories

Puppet Module for ClusterControl - Adding Management and Monitoring to your Existing Database Clusters

If you are automating your infrastructure using Puppet, then this blog is for you. We are glad to announce the availability of a Puppet module for ClusterControl. For those using Chef, we already published Chef cookbooks for Galera Cluster and ClusterControl some time back. 

How to Manage All Your MySQL or MariaDB Databases

According to Forrester, a DBA in a large enterprise manages between 8 and 275 databases, with the industry average being 40 databases to a DBA. Larger databases usually require extra effort around tuning, backup, recovery and upgrade. Cloud, as well as automation and management tools can help improve the number of databases managed by one DBA.

Webinar Replay & Slides: Management & Automation of MongoDB Clusters

Thanks to everyone who attended last week’s joint webinar with the Tokutek Team; if you missed the sessions or would like to watch the webinar again & browse through the slides, they are now available online.

Posted in:

Installing ClusterControl on Existing MongoDB Replica Set using bootstrap script

So, your development project has been humming along nicely on MongoDB, until it was time to deploy the application. That's when you called your operations person and things got uncomfortable. NoSQL, document database, collections, replica sets, sharding, config servers, query servers,... What the hell's going on here?

MongoDB Tutorial - On-premises Cluster Management and Monitoring of MongoDB Replica Set

Replica Sets in MongoDB are very useful. They provide multiple copies of data, automated failover and read scalability. A Replica Set can consist of up to 12 nodes, with only one primary node (or master node) able to accept writes. In case of primary node failure, a new primary is auto-elected.Replica Sets in MongoDB are very useful. They provide multiple copies of data, automated failover and read scalability. A Replica Set can consist of up to 12 nodes, with only one primary node (or master node) able to accept writes. In case of primary node failure, a new primary is auto-elected.