Odin
  • Introduction
  • Why Odin?
  • Key Concepts
    • Environment
      • Environment Type
    • Provisioning
      • Provisioning Config for Component Types
    • Component
      • Available Component Types
      • Component Type reference
        • Optimus Components
          • Aerospike [6.3.0.7-1.0.0]
    • Service
      • Know Your Service Definition
    • Versioning
      • Clearing the Confusion: A Simplified Guide to Artifact, Component, and Service Versions
    • Service Sets
    • Labels
  • Reference
    • CLI reference
  • Onboard Your Service
    • Installation
    • Configure
    • Odin -h
    • Getting Started
    • Create Environment
      • Operations on Environment
    • Service Definition
    • Provisioning Config
    • Deploy Service
    • Release Service
    • Optimus Datastore Operations
      • How to use Optimus Datastore in my service?
      • RDS Operations
      • Aerospike Operations
      • Kafka Operations
    • Operating Service & Components
      • Redeploy
        • In Place Deployment
        • Blue Green Deployment
      • Rolling Restart
      • Adding & removing components
      • Revert a deployment for application component
      • Downscaling a Passive Stack
      • Updating the no. of stacks of application component
    • Dev <> QA iteration
    • Frequently Asked Questions
    • Deploy Concrete Service
    • Undeploy Service
    • Delete Environment
    • Appendix
  • How To
    • Define error threshold for canary deployment
    • Add or Remove a component in an already deployed service
    • Integrate mono-repo(cronjobs) with Odin
    • Deploy crontab with Odin
    • Integrate Data pipeline with Odin
    • Push logs to log central
    • Build artifacts for multi module applications
    • Load test with Odin
    • Track Deployments against Commit Ids
    • Deploy Service on Production - Dream11
    • How and when images are created
    • Check logs for deployed infrastructure - Dream11
    • Onboard Stepfunction as a component
    • Onboard Serverless as a component
    • Login to Kubernetes clusters
  • Release Notes
    • 1.2.0-beta.2 - 11 August, 2022
    • Odin October Release
    • Odin 1.2.0 - Nov 9th 2022
    • Odin February Release
Powered by GitBook
On this page
  • Available Operations
  • Scale
  • Synopsis
Export as PDF
  1. Onboard Your Service
  2. Optimus Datastore Operations

Aerospike Operations

PreviousRDS OperationsNextKafka Operations

Last updated 9 months ago

Please note, Aerospike scaling is currently supported only for new services. For existing services with Aerospike, migration will be needed to avail this capability.

Available Operations

Scale

What does it do

It enables user to modify the capacity of the cluster by changing the count of instances that are already part of the cluster. It uses AWS ASG to balance instances across AZs. It has idempotency to idendify duplicate requests.

This operation is to be performed only via the platform and restricts any actions explicitly done in order to ensure cluster SLAs.

When to use

This operation can be run only when the cluster is in running state or when an existing operation is success. User need to wait if any existing operation is already running on the same cluster and can check its status via odin provided Jenkins.

Limitations

  • Vertical scaling is not supported.

  • Scale operation cannot be stopped.

Prerequisites

  • Cluster must be created by or migrated to Odin and Optimus.

  • Cluster must be in a running state.

  • User must have the necessary permissions to perform the operation.

How to use ?

Insert the desired instance count for the cluster in num_instances

Options

Option
Type
Description
Example

num_instances

integer

The number of EC2 instances needed in the cluster

--options=‘{“num_instances”: 9}’

Synopsis

odin operate component --name [YOUR_COMPONENT_NAME] --service [YOUR_SERVICE_NAME] --operation scale --options=‘{“num_instances”: [YOUR_DESIRED_INSTANCE_COUNT]}’ --env [YOUR_ENV_NAME]

Example

odin operate component --name optimus-aerospike --service optimus-backend --operation scale --options=‘{“num_instances”: 9}’ --env dev1

The above command scales a cluster to 9 instances.

Whom to reach out to ?

Post in Slack channel #dss_odin_feedback

Scale