VECO: configuration/updateConfigurationModule timed out

Products

• VMware Edge Cloud Orchestrator

Issue/Introduction

When attempting to save configuration changes to profiles with a large number of edges attached, the configuration will take a large time to save, and the following error message is displayed in the UI. 

 

Cause

This behavior is due to VECO system property session.options.asyncPollingMaxCount being set to 10 by default. This is an edge case performance issue and the optimization needs to be increased on the VECO. When a configuration update is made an Asynchronous API call is made to apply the configuration. The API call will have to wait for a backend response. With a larger number of edges assigned to a profile, the amount of time the VCO will take to propagate the changes to all the edges will increase. The VCO property session.options.asyncPollingMaxCount is what is used to determine the number of times the VCO will pull the backend with regards to the configuration propagation. As mentioned the default value for session.options.asyncPollingMaxCount is 10, which means that the VCO UI will pull the status only 10 times, if the job hasn't finished at 10th pull, the UI will show timeout although the VCO keeps updating the configuration on the backend. 

 

Resolution

Starting with VECO build 6.1.0 session.options.asyncPollingMaxCount has been increased from 10 to 60. 

Additional Information

session.options.asyncPollingMaxCount is a setting that only affects the web browser to API connection. By increasing the timeout, we are allowing the browser to make additional requests to the API to figure out if the update has gone through. If the API responds back more quickly than the max count, the UI will give the user the success message immediately so there is no side effect. 60 is the new default number for release 6.1. After other use cases we have found that increasing to 60 will alleviate the behavior with the configuration module timing out without putting undue burden on the API's.