Increasing the memory allocated to a vRealize Orchestrator instance

Products

• VMware Aria Suite

Issue/Introduction

This article provides steps for increasing the memory allocated to the vRealize Orchestrator server instance located within the vRealize Automation appliance. By default, the embedded vRealize Orchestrator server is configured to use 3GB memory approximately.

Environment

VMware vRealize Automation 7.x
VMware vRealize Orchestrator 7.x

Resolution

To increase the Java heap memory allocation:

Embedded vRealize Orchestrator 7.x:

1. Open the /usr/lib/vco/app-server/bin/setenv.sh file using a text editor.
2. Modify the memory by setting the Xmx and Xms values to the MB value required:
   
   For example: 2.5 GB memory is allocated to each Xmx and Xms:
   
   JVM_OPTS="$JVM_OPTS -Xmx2560m -Xms2560m -Xmn896m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=1024m -Xss256k"
    
3. Edit the /etc/vr/memory-custom file using a text editor.
4. Add this entry:
   
   add_service_mem vco-server 3072
   
   Note: The number is equal to the sum of -Xmx and -MetaspaceSize as configured in step #1. The memory is in MB.
    
5. Stop the vRealize Appliance and increase/decrease the memory to match the increased/decreased memory of the vRealize Orchestrator.
6. Start the vRealize Appliance.
7. Repeat steps #1 to #6 to rest of the nodes in the cluster.

External vRealize Orchestrator 7.x:

1. Open the /usr/lib/vco/app-server/bin/setenv.sh file using a text editor.
2. Modify the memory by setting the Xmx and Xms values to the MB value required.

For example 2.5 GB memory is allocated to each Xmx and Xms:
JVM_OPTS="$JVM_OPTS -Xmx2560m -Xms2560m -Xmn896m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=1024m -Xss256k"

3. ​Stop the vRealize Orchestrator Appliance and increase/decrease the memory to match the increased/decreased memory of the vRealize Orchestrator.
4. Start the vRealize Orchestrator Appliance.
5. Repeat steps #1 to #4 to rest of the nodes in the cluster.

Windows installation of vRealize Orchestrator 6.x:

1. Open the %ProgramFiles(x86)%/VMware/Orchestrator/app-server/bin/wrapper.conf file using a text editor.
2. Depending on the available memory on your vRealize Orchestrator server, adjust the value appropriately. Ensure that there is enough additional free memory for the operating system and other components.
   
   To increase heap (in this example it is to 6GB):
    
   1. Add this line:
      
      wrapper.java.additional.NN="-Xmx6144m"
      
      Where, NN is the next number in the list.
       
   2. Set the value of java maximum memory by modifying the maxmemory line to:
      
      /usr/lib/vco/app-server/bin/setenv.sh file using a text editor.
   3. Modify the memory by setting the Xmx and Xms values to the MB value required.
      
      For example: 2.5 GB memory is allocated to each Xmx and Xms:
      
      JVM_OPTS="$JVM_OPTS -Xmx2560m -Xms2560m -Xmn896m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=1024m -Xss256k"
       
   4. Stop the vRealize Orchestrator Appliance and increase/decrease the memory to match the increased/decreased memory of the vRealize Orchestrator.
   5. Start the vRealize Orchestrator Appliance.
   6. Repeat steps# 1 to #4 to rest of the nodes in the cluster.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box..

Impact/Risks:

When modifying this setting, ensure to increase your overall appliance memory if needed to prevent impact to other components running on the vRealize Automation appliance.

For further information on increasing a virtual appliance(s) memory, see the below Steps :

Use these instructions if you want to change the memory configuration of a virtual machine's hardware.

From the vCenter client, power off the virtual appliance.
Select the VM, and right-click to Edit Settings.
With the Hardware tab selected, select Memory.
On the right window pane, increase the Memory Size.
Click OK.
Power on and reboot the VM.  

If you do not increase the memory of the vRealize Appliance when you increase the memory of the vRealize Orchestrator, this will effectively decrease the memory of the vRealize Appliance and vIDM. If you change only the setenv.sh file, the vRealize Appliance will start swapping as the memory will be over committed.