Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to scale up Cloud Director Availability 4.x for large scale environments (79217)

Last Updated: 1/16/2024Categories: How toTotal Views: 3741Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides information on how to scale up a Cloud Director Availability deployment in a large scale cloud environment, where Cloud Director Availability is managing over 6000 replications.

Resolution

In the large scale environment it is recommended to perform the following steps in order to avoid out of memory errors on the Cloud Director Availability appliances.

Note: The following process only needs to be applied to the Cloud Replication Management, Replicator, and Tunnel appliances on a cloud site. No actions are required on On-Premises appliances.

Increase the memory of the Cloud Replication Management appliance

Log into the vSphere Client where you can manage the Cloud Director Availability appliances.

Power off the Cloud Replication Management appliance.

Right-click on the appliance and click Edit Settings.

In the Virtual Hardware section, increase the CPUs from 2 cores to 4 cores.

In the Virtual Hardware section, increase the memory from 4GB to 12GB.

Click OK.

Power on the Cloud Replication Management appliance.

Configure the Cloud Director Availability appliances

Cloud service

SSH to the Cloud Replication Management appliance and log in as root.

Navigate to the Cloud Service configuration directory:

cd /opt/vmware/h4/cloud/config

Take a backup of the application.properties file:

cp application.properties application.properties.bak

Append the application.properties file with the following lines:

spring.jpa.properties.hibernate.query.plan_cache_max_size=256
spring.jpa.properties.hibernate.query.plan_parameter_metadata_max_size=64
spring.jpa.properties.hibernate.query.in_clause_parameter_padding=true

(Optional) If you plan to start more than 100 concurrent protections, uncomment the jobengine.threads.per.user line and double the value:

# Maximum number of allowed threads per user
jobengine.threads.per.user=20

Note: From Cloud Director Availability 4.7 onwards, you no longer need to increase the maximum number of allowed threads per user when you want to start a large number of concurrent protections. If you are using Cloud Director Availability 4.7 or later, skip step 5 and proceed directly to step 6.

(Optional) If you plan to replicate vApp Templates and leverage automatic vApp Template protection, uncomment the vcd.vapp.settings.timeout line and double the value:

vcd.vapp.settings.timeout=600000

Restart the Cloud service for the changes to take effect:

systemctl restart cloud

Manager service

SSH to the Cloud Replication Management appliance and log in as root.

Navigate to the Manager Service configuration directory:

cd /opt/vmware/h4/manager/config

Take a backup of the application.properties file:

cp application.properties application.properties.bak

Append the application.properties file with the following lines:

spring.jpa.properties.hibernate.query.plan_cache_max_size=256
spring.jpa.properties.hibernate.query.plan_parameter_metadata_max_size=64
spring.jpa.properties.hibernate.query.in_clause_parameter_padding=true

(Optional) If you plan to start more than 100 concurrent protections, uncomment the jobengine.threads.per.user line and double the value:

# Maximum number of allowed threads per user
jobengine.threads.per.user=20

Note: From Cloud Director Availability 4.7 onwards, you no longer need to increase the maximum number of allowed threads per user when you want to start a large number of concurrent protections. If you are using Cloud Director Availability 4.7 or later, skip step 5 and proceed directly to step 6.

Append the application.properties file with the following lines:

sync.scheduler.thread.count=100
health.scheduler.thread.count=100

Restart the Manager service for the changes to take effect:

systemctl restart manager

Replicator service

SSH to the Replicator appliance and log in as root.

Navigate to the Replicator Service configuration directory:

cd /opt/vmware/h4/replicator/config

Take a backup of the application.properties file:

cp application.properties application.properties.bak

Append the application.properties file with the following lines:

spring.jpa.properties.hibernate.query.plan_cache_max_size=256
spring.jpa.properties.hibernate.query.plan_parameter_metadata_max_size=64
spring.jpa.properties.hibernate.query.in_clause_parameter_padding=true

(Optional) If you plan to start more than 100 concurrent protections, uncomment the jobengine.threads.per.user line and double the value:

# Maximum number of allowed threads per user
jobengine.threads.per.user=20

 Note: From Cloud Director Availability 4.7 onwards, you no longer need to increase the maximum number of allowed threads per user when you want to start a large number of concurrent protections. If you are using Cloud Director Availability 4.7 or later, skip step 5 and proceed directly to step 6.

Restart the Replicator service for the changes to take effect:

systemctl restart replicator

Tunnel service

SSH to the Tunnel appliance and log in as root.

Navigate to the systemd services directory:

cd /lib/systemd/system

Update the LimitNOFILE line in the tunnel.service file:

LimitNOFILE=40960

Restart the Tunnel service for the changes to take effect:

systemctl restart tunnel

Related Information

For more information on the scale limit for active protections per Replicator instance, see VMware Configuration Maximums.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
VMware vRealize Automation 的内部版本号和版本 (2143850)

KB
•
VMware vCloud Director 和 VMware vCloud Connector 的内部版本号和版本 (2143847)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Availability

Related Versions:

VMware Cloud Director Availability 4.x

Take Our Survey

Support Assistant