API configuration load fails or takes a long time on APIs with version number >300

Solution Unverified - Updated -

Issue

  • How can old API versions be deleted?
  • Does the parameter THREESCALE_DEPLOYMENT_ENV have any effect on the service configuration loading?
  • APIs with lots of changes made, (version count >300). The apicast gateway fails to load the service configuration with a timeout error.
    In general there is an increasing response time with increasing number of versions per API.

Environment

  • Red Hat 3scale API Management 2.5.0 On-Premises

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In