Reprovision universe nodes
Starting in YugabyteDB Anywhere v2026.1.2.0, you can re-run node provisioning on an existing universe so OS-level settings match what the current YugabyteDB Anywhere expects. For universes still on legacy provisioning, the action also migrates the nodes to use automatic provisioning, including node agent and user-level systemd.
Your data is preserved. Only the OS and node agent layers are reprovisioned; database software and data volumes remain untouched.
The action applies the following OS settings:
- Process and open-file limits (
nofile,nproc) - Transparent hugepages (THP)
- Clock synchronization (chrony / ClockBound)
- Kernel/sysctl values (for example,
vm.swappiness,vm.max_map_count, core dump pattern)
When to reprovision
YugabyteDB Anywhere surfaces when reprovisioning would help:
- A banner indicates that universe nodes need to migrate to node agent or off legacy provisioning.
- Health checks report OS-setting drift on a node. For example, a process-limit or open-file warning, THP flagged as misconfigured, or a clock/NTP synchronization issue.
The action is always available on supported universes (the same as Reinstall Node Agent). Run it when YugabyteDB Anywhere indicates one of the above, or when you want to apply current OS settings. This is not a prerequisite for upgrading to v2025.2; treat it like a patch to keep database nodes updated.
Reprovisioning performs a rolling restart, the same as a node resize or VM image upgrade. Perform it during a low-traffic period and avoid scheduled backup windows.
Replication factor less than 3
If the universe replication factor is less than 3, the universe is not available for reads and writes while nodes restart.Limitations
This action is not available for Kubernetes universes.
| Deployment type | Support |
|---|---|
| Public cloud (AWS, GCP, Azure) | Full UI and API support. |
| On-premises (with passwordless sudo) | Full UI and API support. |
| On-premises, manual (no passwordless sudo) | Not supported. The UI hides the action. The API returns an error. Use the node-agent-provision.sh script instead. |
This action does not replace patching the Linux OS or replacing a boot disk. After a boot disk replacement, continue to follow that procedure, which reinstalls YugabyteDB software on the node.
Reprovision nodes
To reprovision nodes, do the following:
-
Navigate to your universe.
-
Click Actions > More > Reprovision Universe Nodes.
-
Choose which nodes to reprovision:
- All nodes in this Universe reprovisions every node, one at a time.
- Selected node targets a single node. This option is unavailable for single-node universes.
-
Click Reprovision Universe Nodes.
YugabyteDB Anywhere starts a ProvisionUniverseNodes task. For each node, it does the following:
- Verifies the node is safe to take down.
- Stops YB-Master, YB-TServer, and YB Controller processes.
- Provisions the nodes.
- Starts the processes again, and waits for the server to be ready.
The task is rolling, abortable, and retryable.
Use the API
To reprovision all nodes:
curl '<platform-url>/api/v1/customers/<customer_uuid>/universes/<universe_uuid>/upgrade/provision_nodes' -X 'POST' -H 'X-AUTH-YW-API-TOKEN: <api-token>' -H 'Content-Type: application/json' -H 'Accept: application/json, text/plain, */*' \
--data-raw '{"nodeNames":[]}'
An empty nodeNames array means all nodes in the universe. To target a single node, pass that node's name:
curl '<platform-url>/api/v1/customers/<customer_uuid>/universes/<universe_uuid>/upgrade/provision_nodes' -X 'POST' -H 'X-AUTH-YW-API-TOKEN: <api-token>' -H 'Content-Type: application/json' -H 'Accept: application/json, text/plain, */*' \
--data-raw '{"nodeNames":["<node_name>"]}'
For information on creating an API token, refer to API authentication.