Search the VMware Knowledge Base (KB)
View by Article ID

Increasing the memory allocated to a vRealize Orchestrator instance (2147109)

  • 0 Ratings

Purpose

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.

Resolution

To increase the memory allocation:
  
In Embedded vRealize Orchestrator Server
  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.
 
In Windows installation of vRO 6.0.x:
 
  1. Open the Program Files/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:

      wrapper.java.maxmemory=0

      Note: maxmemory must be set to  0 to allow Xmx to be used.

      For example, extract of the wrapper.conf file:

      wrapper.java.additional.20="-Djavax.net.ssl.trustStorePassword=dunesdunes"
      wrapper.java.additional.21="-Djsse.enableSNIExtension=false"
      wrapper.java.additional.22="-Djava.io.tmpdir=%CATALINA_BASE%\temp"
      wrapper.java.maxmemory=4096

      Changes to:

      wrapper.java.additional.20="-Djavax.net.ssl.trustStorePassword=dunesdunes"
      wrapper.java.additional.21="-Djsse.enableSNIExtension=false"
      wrapper.java.additional.22="-Djava.io.tmpdir=%CATALINA_BASE%\temp"
      wrapper.java.additional.23="-Xmx6144m"
      wrapper.java.maxmemory=0

  3. Make the same changes to the Program Files/VMware/Orchestrator/app-server/bin/wrapper-auto.conf file.


In vRealize Orchestrator Appliance versions 6.0.4, 6.0.5 and 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.

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.  
 
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.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: