You may need to increase CPU, memory, or disk capacity for a stateful node running on Azure to support growing workloads or performance requirements.
Flexera supports different update methods depending on whether you are changing disk size or compute resources. This article explains what can be updated and where each change must be made.
Update OS disk and data disk size
You can increase the size of the OS disk and data disks used by a stateful node.
Supported options
-
Use the Flexera API to update disk sizes.
-
Edit the stateful node configuration JSON in the Flexera console.
Update disk size using the API
You can update the OS disk and data disk size using the Azure stateful node update API:
Update disk size using the console
-
In the Flexera console, open the stateful node.
-
Select Edit node, then go to Review and open JSON in Edit mode.
-
Update the
osDiskordataDisksize values as needed. -
Save the configuration and apply the changes.
Update CPU and memory
CPU and memory sizing are controlled by the Azure VM size, not by disk configuration.
Important limitations
-
You cannot update memory size directly from the Flexera console.
-
Azure does not support dynamically resizing RAM without changing the VM size.
Available options
-
Change the VM size in your stateful node configuration to a size with more CPU or memory.
-
Resize the virtual machine directly in the Azure portal.
To review available VM sizes and their CPU and memory characteristics, see:
For Azure platform guidance on resizing memory, see:
After completing these steps:
-
OS disk and data disk sizes are updated for the stateful node.
-
CPU and memory changes take effect after resizing the VM or selecting a new VM size.
-
The stateful node continues running with the updated resource configuration.
Related Articles
Increase disk size for Azure stateful nodes 5Number of Views Increase the volume size for a stateful instance 4Number of Views Resolve the “no data to display” message for memory utilization on a stateful node 6Number of Views Convert a stateful node into a stateful Elastigroup 5Number of Views Fix stateful node import or launch failures caused by disk redundancy and zone settings 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago