check-resource takes a long time to complete after upgrading to Concourse 6.3.0 or newer

Products

• Concourse for VMware Tanzu

Issue/Introduction

After upgrading to Concourse v6.3.0 or newer, it may take a very longer time for check-resource to complete and in specific environments, the “preparing build” section shows the following message on the web console.

discovering any new versions of <resource name>
waiting for a suitable set of input versions
* <resource name> - checking for latest available versions

In the worst case, it takes more than a hour to finish check-resource. In versions of Concourse prior to v6.3.0,  check-resource finishes in a few seconds.

Environment

Product Version: 6.3

Resolution

This issue could be caused by rate limit optimization (v6.3.0), which has been a new feature of Runtime since Concourse v6.3.0.

To work around this issue, set the max-checks-per-second flag to -1 to turn off the new rate limit optimization behavior.

Concourse for VMware Tanzu product based on a BOSH release

1. In the case of setting the flag with Concourse for VMware Tanzu product based on a BOSH release, you add the  max_checks_per_second property and set it to -1 in the deployment manifest (concourse.yml) as below:

---
name: ((deployment_name))

releases:
- name: concourse
  :
instance_groups:
- name: web
  instances: 1
  azs: ((azs))
    :
  - release: concourse
    name: web
    properties:
      token_signing_key: ((token_signing_key))
        :
      max_checks_per_second: -1
        :

2. Redeploy your Concourse BOSH release on your BOSH environment and you can turn off the limit optimization behavior.