You can access the "Couchbase Server - Community Edition" ServerTemplate published by Couchbase from the MultiCloud Marketplace.
The ServerTemplate has numerous inputs that are used to configure the instance when it's launched. Many of these inputs have default values that can be modified, if desired. Note that the same input may be used by more than one script and in some cases will take on a slightly different meaning for that script.
Table of Contents
The following Boot Scripts are listed in order.
MON_PROCESSES | memcached
SERVER_UUID | RS_INSTANCE_UUID
SKETCHY | RS_SKETCHY
CB_PASS | $ignore - Used to denote the password for the server that this instance is attempting to join. Note that this does not actually apply the password to the running instance, it is simply used for connecting to the remote cluster.
CB_USER | $ignore - Used to denote the username for the server that this instance is attempting to join. Note that this does not actually apply the username to the running instance, it is simply used for connecting to the remote cluster
While no Decommission Scripts are provided by default, the Operational Script "Couchbase Server - Leave Cluster" can be used as a decommission script. Make sure that the "Couchbase Server - Delay Decommission" script is set to run on boot and that the decommission delay is long enough for the rebalancing event to take place (the default one hour setting should be plenty of time).
Note: This runbook is not meant to provide a substantial background of the underlying architecture of Couchbase. Documentation for Couchbase Server itself can be found at http://www.couchbase.com/docs
Note: Applies only to the "Couchbase Enterprise Edition" ServerTemplate.
When using Couchbase in a production and mission critical environment, it is best to have a disaster recovery plan in the event that all servers within a cluster are lost. Couchbase is designed to be highly available via a user-configurable number of replicas. However, a total cluster outage will require the data to be reloaded from disk. The only way to recover your data in EC2 is by using EBS volumes that will persist even after its instance has been terminated.
The two prerequisites to performing a recovery is that all Couchbase servers were originally configured to use a DNS name (via the DNS_ID input to the ServerTemplate) and that all the Couchbase servers were configured to use an EBS volume (via the CB_USE_EBS input). All data and configuration information is saved on the EBS volume. Additionally, the volume will have been automatically renamed to match the DNS_ID provided so that the administrator can properly signal the RightScale recovery process.
To recover an instance that had its configuration and data saved on an EBS volume:
Create a new server from the same ServerTemplate as the original instance.
Set the DNS_ID of the new instance to be the same value as the instance you are recovering.
Set the CB_INITIAL_LAUNCH value to FALSE and make sure the CB_USE_EBS is still set to TRUE.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.