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

"Could not obtain exclusive access to the vApp for replication..." error when failing over multiple VMs concurrently in Cloud Director Availability (79405)

Last Updated: 12/9/2020Categories: Known IssueTotal Views: 2744Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Performing a failover, test failover, or test cleanup for multiple VMs in the same protection group or vApp simultaneously fails.

In /opt/vmware/h4/cloud/log/cloud.log on the Cloud Replication Management Appliance, you see a similar error:

2020-05-18 09:02:17.005 ERROR - [UI-6d06ab27-dc8c-43c7-b00b-8faf5ad5e077-ro-iJ_n93] [c4-scheduler-1] com.vmware.h4.jobengine.JobExecution  : Task 13bab05b-47a0-483b-9d6a-33e5453393ec (WorkflowInfo{type='failoverTest', resourceType='vmReplication', resourceId='C4-cbe6d486-860e-49dc-ba50-66b27c61c2be', isPrivate=false, resourceName='Test8RHE'}) has failed

com.vmware.h4.cloud.api.exceptions.VappLockedException: Could not obtain exclusive access to the vApp for replication 'C4VAPP-5cb691cb-d1d0-41a3-b533-6510eff7dcce' because another failover for a vm from the same vApp has locked it.

at com.vmware.h4.cloud.job.VmFailoverJob.lambda$importIntoVcd$6(VmFailoverJob.java:350)

at com.vmware.h4.jobengine.lock.JobLock.lambda$lock$2(JobLock.java:92)

at com.vmware.h4.jobengine.lock.LockManager.invokeHandler(LockManager.java:286)

at com.vmware.h4.jobengine.lock.LockManager.expire(LockManager.java:269)

at com.vmware.h4.jobengine.lock.LockManager.lambda$obtain$1(LockManager.java:179)

at com.vmware.h4.common.mdc.MDCRunnableWrapper.run(MDCRunnableWrapper.java:30)

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)

at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs because Cloud Director Availability starts all VM failover jobs in parallel, but the tasks become serialized in Cloud Director as they attempt to obtain lock for the same target vApp.

The first failover job that obtains that lock does so for the whole failover process and the rest of the VMs wait. Once the lock is released, the next job that manages to obtain it proceeds with its failover and so on until all VMs have been failed over.

The default timeout for obtaining a vApp lock is 10 minutes, if a VM fails to acquire lock within these 10 miuntes then the failover task fails.

Resolution

This is a known issue affecting Cloud Director Availability 4.x.
Currently, there is no resolution.

Workaround

To work around this issue, perform the failover or test failover one VM at a time for each of the failed VMs.

Note: Don't retry the failover on the vApp level again because this will delete the already successful failovers.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
AppDefense アプライアンス SSL 証明書の更新 (76768)

KB
•
[VMC on AWS] SDDC 内の大規模な NSX Edge の CPU とメモリの使用率が高い (80679)

Results 1-2 of 2

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 vCloud Availability 3.5.x

VMware vCloud Availability 3.0.x

VMware Cloud Director Availability 4.x

Take Our Survey

Support Assistant