Object Storage Extension experiences slowness when VMware Cloud Director multi-site is configured
search cancel

Object Storage Extension experiences slowness when VMware Cloud Director multi-site is configured

book

Article ID: 371513

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • All the Object Storage Extension (OSE) API calls take long time to complete like: API to List Platform Capabilities, API to list the storage classes, API to list current associated tenants and API to get the tenants usage.
  • VMware Cloud Director (VCD) multisite is configured.
  • Only one VCD site has OSE configured.
  • From the debug.log on the OSE node you see entries similar the one reported below:

    YY/MM/DD TIME [XNIO-2 task-4] DEBUG c.v.v.service.impl.VCloudServiceImpl - I/O error on GET request for "https://example.vcloud.com/api/versions": Connect to example.vcloud.com:443 [example.vcloud.com/XX.XX.XX.XX] failed: Connection timed out (Connection timed out); nested exception is org.apache.http.conn.HttpHostConnectException: Connect to example.vcloud.com:443 [example.vcloud.com/XX.XX.XX.XX] failed: Connection timed out (Connection timed out)

Environment

Object Storage Extension 2.2.x
VMware Cloud Director 10.x

Cause

Since VCD multi-site is configured, OSE will query both site to aggregate result.
If the OSE endpoint cannot access one of the remote site, OSE needs to wait until the timeout for each request, causing long time to return for each  API call.

Resolution

Ensure that both site can be accessed by the local OSE endpoint.