Summer Project 2016: The CouchCase
Summer Project 2016: The CouchCase
As the last part of the series on his summer project, CouchCase, Matthew Groves shares with us how he clustered Couchbase Server nodes. Read on to find out more.
Join the DZone community and get the full member experience.
Join For FreeCompliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper
I know that Summer 2016 is long gone, but I promised one more blog post about building the CouchCase. This part was the easiest, seeing as clustering Couchbase Server nodes together is really easy.
Networking
First, a little information about how I networked the Intel Compute Sticks. On the router in the CouchCase, I’ve pegged each network adapter to a specific IP address. How to do this is going to vary from router to router, so consult your manual.
Here’s a snapshot of STICK1, STICK2, and STICK3 all pegged to three IP addresses and attached to the router.
Clustering
The first time you setup Couchbase Server, you are creating a cluster with a single node. So, if you’ve done this, as far as setting up an entire cluster, you are most of the way there.
Next, install Couchbase Server on another machine (or VM or whatever). Instead of selecting "Start a new Cluster", select "Join a cluster now." Enter the IP address of the first node you created, as well as the username/password information that you set it to be.
Once you do that, you should get a message saying "This server has been associated with the cluster and will join on the next rebalance operation."
A rebalance operation is necessary for Couchbase to figure out all the details of which node a given document should live on. For more information, check out the documentation on Rebalancing a Cluster.
A rebalance is a background operation, and should not interfere with the operation of nodes that are already working. This means that if you need to add capacity to your database, you don’t have to take down your website or schedule a 'maintenence window' or anything like that.
Once the rebalance is complete, you should see a list of nodes:
And there you have it! The CouchCase is ready for the road. You've seen how to network and cluster your Couchbase Server nodes, as well as handle a few of the hiccups that can crop up along the way, such as rebalancing. That's all! Enjoy autumn.
Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper
Like This Article? Read More From DZone
Published at DZone with permission of Matthew Groves , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}