TeamCity On-Premises
 
You are viewing the documentation for an earlier version of TeamCity On-Premises.

Multinode Setup

Last modified: 11 March 2021

TeamCity allows configuring and starting one or more secondary server instances (nodes) in addition to the main one. The main and secondary nodes operate under the same license and share the TeamCity Data Directory and the database.

Using the multinode setup, you can:

  • Set up a high-availability TeamCity installation that will have zero downtime for most operations. Secondary nodes will operate as usual during the downtime of the main server (for example, during the minor upgrades).

  • Improve the performance of the main server by delegating tasks to the secondary nodes. A secondary node can detect new commits and process data produced by running builds (build logs, artifacts, statistic values).

After installation, each secondary node runs as a read-only copy of the main server. To extend its functionality, you can assign it to a certain responsibility. In this case, the secondary node will allow users to perform the most common actions on builds.

The following diagram shows an example of a TeamCity installation with one main node and two secondary nodes, where each secondary node has a certain responsibility:

TeamCity setup with two nodes