High Availability (HA) in Octopus enables you to run multiple Octopus Server nodes, distributing load between them. There are two kinds of load a Server node encounters:
- Tasks (Deployments, runbook runs, health checks, package re-indexing, system integrity checks, etc.)
- User Interface via the Web UI and REST API (Users, build server integrations, deployment target registrations, etc.)
Deploying a release or triggering a runbook run places that work into a first-in, first-out (FIFO) task queue. You can view the task queue by navigating to the TASKS page on your Octopus Deploy instance. Deployments and runbook runs are not the only items placed into the task queue.
Some other examples of tasks include (but are not limited to):
- Apply Retention policies
- Delete Space
- Export Projects
- Health check
- Import Projects
- Let’s Encrypt
- Process recurring scheduled tasks
- Process subscriptions
- Script Console Run
- Sync Community Step templates
- Sync External Security Groups
- Tentacle upgrade
- Update Calamari
By default, each Octopus Deploy node is configured to process five (5) tasks concurrently. That is known as the task cap. It is possible to change the task cap on each node.
While it is possible to increase the task cap on a single node to 50, 75, or even 100, you’ll eventually run into the underlying host OS and .NET limits. A server can only open up so many network connections, transport so many files, and run so many concurrent threads. High Availability solves that problem by scaling the task cap horizontally. Each node will pull items from the task queue and process them.
How Tasks are distributed between HA nodes
Every 20 seconds, each node in the HA cluster will check the task queue for pending tasks. When pending tasks are found, the node will start processing them.
Octopus will do its best to balance the load between all the nodes to ensure one node doesn’t process all the tasks while the other nodes remain unused. It does that by comparing the current node workload ratio with the prospective cluster workload ratio.
The current node workload ratio is defined as
(active tasks on node / node limit). The prospective cluster workload ratio is defined as
(active cluster tasks + pending tasks / max cluster tasks).
A node will not pick up pending tasks when:
- The node is in drain mode (a toggle preventing the node from executing new tasks).
- The number of active tasks is equal to or greater than the task cap.
- The current node workload ratio is greater than the prospective cluster workload ratio.
The last item in that list needs a deeper dive to understand. For this example, we have a cluster with three nodes, each with a task cap set to ten (10). Thus, making the HA cluster’s total task capacity 30. There are 12 pending tasks in the queue and 10 active tasks.
Lets assume all three nodes check the task queue at the same time. The prospective cluster workload ratio is 73.34% (12 pending tasks + 10 active tasks / 30 task capacity).
- One node is currently processing eight tasks making the current node workload ratio 80% (8/10). While this node can pick up two more tasks, it will not because 80% > 73.34%.
- One node is currently processing three tasks making the current node workload ratio 30% (3/10). It can pick up seven more tasks but will only pick up five more tasks. It picks up tasks until its current node workload ratio is greater than the prospective cluster workload ratio.
- One node is not processing any tasks. It will pick up all the remaining seven tasks.
There are a few considerations this example did not take into account.
- Not every node checks the task queue at the same time. The timer is based on the last time node was restarted.
- 1 to N tasks could be added to the queue between node 1 checking the queue and nodes 2 and 3 check the queue.
- 1 to N tasks could be completed between node 1 checking the queue and nodes 2 and 3 check the queue.
First-in, first-out queue
The task queue is a first-in, first-out (FIFO) queue. The node does not consider the task type, the expected duration of the task, the environment the task is configured to run on, or any other factors. Being a FIFO queue, combined with task distribution logic, this can result in one node processing all deployments while other nodes processing runbook runs or health checks. When that happens, it was just luck.
Restarting the server during an active deployment
Restarting the Octopus Deploy windows service or the underlying host OS will (eventually) cause any active tasks to fail. At first, the tasks will look like they are still in process. Once the node comes back online, it will cancel all active tasks. If the node doesn’t come back online within an hour, one of the other nodes will cancel those tasks.
For planned outages, the recommendation is to enable drain mode. That will tell the node to finish up all active tasks and not pick up any new ones. That can be achieved by:
- Navigating to Configuration ➜ Nodes.
- Clicking on the overflow menu (
...) next to the node you plan on restarting.
- Selecting Drain Node.
Once the outage is finished, repeat the same steps, but select Disable Drain Node instead.
Not all outages can be planned. The underlying hypervisor hosting VM the node is running on could crash. A data center could go offline. When that happens you can use this API Script to re-run those canceled deployments and runbook runs.
Several smaller nodes are better than a few large ones
We recommend several smaller nodes, each with 4 CPUs and 8 GB of RAM, over two or three large nodes, each with 16 CPUs and 64 GB of RAM. In our testing, 4 CPUs and 8 GB of RAM can handle around 20 concurrent tasks.
Assuming you’d want to be able to process 80 tasks concurrently.
- If you had two nodes, each with a task cap of 40, an outage on one node would reduce your capacity by 50%.
- If you had four nodes, each with a task cap of 20, an outage on one node would reduce your capacity by 25%.
If you are hosting your virtual machines on a cloud provider, the cost difference between 2 VMs with 8 CPUs / 16 GB of RAM and 4 VMs with 4 CPUs / 8 GB of RAM is minimal.
Octopus Deploy provides two main interfaces for our users.
- Web Portal
- REST API
All other tools, including the CLI, build server plug-ins, etc., are wrappers around the REST API. All communication to the Web Portal or REST API occurs over standard web server ports, 80 or 443. Because of that, you will need a load balancer to distribute traffic between the nodes.
Help us continuously improve
Please let us know if you have any feedback about this page.
Last updated Sunday, January 1, 2023