> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2026.2/server-update-and-maintenance/data-center-edition/scaling.md).

# Scaling

You have the option of adding application nodes (up to 10 total application nodes) to your cluster to increase computing capabilities. The operation is different depending on the SonarQube Server installation type.

## ZIP installation <a href="#zip-installation" id="zip-installation"></a>

### Adding an Application Node <a href="#adding-an-application-node" id="adding-an-application-node"></a>

To add an application node:

1. Configure your new application node in sonar.properties. The following is an example of the configuration to be added to `sonar.properties` for a sixth application node (server6, ip6) in a cluster with the default five servers. For information about the system properties used, see [List of DCE-specific properties](/sonarqube-server/2026.2/server-installation/system-properties/dce-specific.md#general).<br>

   **Server6:**

```css-79elbk
...
sonar.cluster.enabled=true
sonar.cluster.node.type=application
sonar.cluster.node.host=ip6 
sonar.cluster.node.port=9003
sonar.cluster.node.web.port=4023
sonar.cluster.node.ce.port=4024
sonar.cluster.hosts=ip1,ip2,ip6
sonar.cluster.search.hosts=ip3:9001,ip4:9001,ip5:9001
sonar.auth.jwtBase64Hs256Secret=YOURGENERATEDSECRET
...
```

{% hint style="info" %}
In the example:

* The hosts followed by ports are written using the IPv4 notation (e.g. `ip3:9001`). If you use IPv6 addresses, enclose the IP address in square brackets (`[ip3]:9001`).
* The `sonar.cluster.node.web.port` and `sonar.cluster.node.ce.port` system properties are used but are optional. If not used, a dynamic port will be chosen.
  {% endhint %}

2. Update the configuration of the preexisting nodes to include your new node. While you don’t need to restart the cluster after adding a node, you should ensure the configuration is up to date on all of your nodes to avoid issues when you eventually do need to restart.

### Removing an Application Node <a href="#removing-an-application-node" id="removing-an-application-node"></a>

When you remove an application node, make sure to update the configuration of the remaining nodes. Much like adding a node, while you don’t need to restart the cluster after removing a node, you should ensure the configuration is up to date on all of your nodes to avoid issues when you eventually do need to restart.

## Docker installation <a href="#docker-installation" id="docker-installation"></a>

### Adding Application Nodes <a href="#adding-application-nodes" id="adding-application-nodes"></a>

If you’re using docker-compose, you can scale the application nodes using the following command:

`docker-compose up -d --scale sonarqube=3`

### Removing Application Nodes <a href="#removing-application-nodes" id="removing-application-nodes"></a>

You can reduce the number of application nodes with the same command used to add application nodes by lowering the number.

## Kubernetes installation <a href="#kubernetes-installation" id="kubernetes-installation"></a>

With Kubernetes’ Horizontal Pod Autoscaling (HPA), you can automatically scale your SonarQube Server out and in, resolving any performance issues you may have. See [Setting up autoscaling](/sonarqube-server/2026.2/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-autoscaling.md).

## Related pages <a href="#related-pages" id="related-pages"></a>

* [DCE topology](/sonarqube-server/2026.2/server-installation/data-center-edition/dce-topology.md)
* [Starting and stopping cluster](/sonarqube-server/2026.2/server-installation/data-center-edition/starting-stopping-cluster.md)
* [Monitoring](/sonarqube-server/2026.2/server-update-and-maintenance/data-center-edition/monitoring.md) your cluster
* [Improving performance](/sonarqube-server/2026.2/server-update-and-maintenance/data-center-edition/improving-performance.md) of your cluster
* [Updating](/sonarqube-server/2026.2/server-update-and-maintenance/data-center-edition/updating.md) your cluster


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/2026.2/server-update-and-maintenance/data-center-edition/scaling.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.