Setting request timeout

Beta

This product or feature is in a pre-release state and might change or have limited support. For more information, see Product launch stages.

This page assumes you have set the following gcloud properties:

• For Cloud Run:

  gcloud config set run/region [REGION]

  replacing [REGION] with the region you are using for your service.
• For Cloud Run on GKE:
  

  gcloud config set run/cluster [CLUSTER]
  gcloud config set run/cluster_location [CLUSTER_LOCATION]

  replacing [CLUSTER] and [CLUSTER_LOCATION] with the name and location of the cluster you are using.
• If you develop for BOTH Cloud Run and Cloud Run on GKE, you cannot set the properties as described above, because they will conflict. Instead, supply the --region parameter as needed in the gcloud command line for Cloud Run , and supply the --cluster and --cluster-location parameters as needed in the gcloud command line for Cloud Run on GKE.

Cloud Run locations

Cloud Run is regional, which means the infrastructure that runs your Cloud Run services is located in a specific region and is managed by Google to be redundantly available across all the zones within that region.

Meeting your latency, availability, or durability requirements are primary factors for selecting the region where your Cloud Run services are run. You can generally select the region nearest to your users but you should consider the location of the other GCP products that are used by your Cloud Run service. Using GCP products together across multiple locations can affect your service's latency as well as cost.

Cloud Run is available in the following regions:

• us-central1 (Iowa)

If you already created a Cloud Run service, you can view the region in the Cloud Run dashboard in the GCP Console.

OK

The request timeout setting specifies the time within which a response must be returned by services deployed to Cloud Run. If a response isn't returned within the time specified, the request ends and error 504 is returned.

By default, the timeout is set to 5 minutes. You can change this setting when you deploy a container image or by updating the service configuration.

In addition to changing the Cloud Run request timeout, you should also check your language framework to see whether it has its own request timeout setting that you must also update. For example, Node.js developers need to update the server.timeout property.

Setting and updating request timeout

You can set the request timeout using the gcloud command-line tool.

Console

1. Go to Cloud Run

2. Click CREATE SERVICE if you are setting request timeout on a new service you are deploying to. If you are setting the timeout on an existing service, then click on the service, then click DEPLOY NEW REVISION.

3. Click SHOW OPTIONAL SETTINGS:

   

   Specify the desired timeout value in the Request timeout textbox, in seconds. using values from 1 to 900 seconds (15 minutes).

4. Click Create or Deploy.

Command line

You can update the request timeout for a given revision at any time by using the following command:

gcloud beta run services update [SERVICE] --timeout=[TIMEOUT]

Replace

• [SERVICE] with the name of your service.

• [TIMEOUT] with the desired time, using an integer value or an absolute duration value, for example 1m20s which is 1 minute, 20 seconds. If you use an integer value, the unit is assumed to be seconds. The value you specify must be less than 15 minutes.

  Note: When you update your service with the new timeout value, a new revision is created.

You can also set the request timeout during deployment using the command:

gcloud beta run deploy --image gcr.io/[PROJECT-ID]/[IMAGE] --timeout=[TIMEOUT]

Replace

• [PROJECT-ID] with your GCP project ID.
• [IMAGE] with the name of your image.
• [TIMEOUT] with the desired time, using an integer value or a duration value, for example 1m20s which is 1 minute, 20 seconds. If you use an integer value, the unit is assumed to be seconds. The value you specify must be less than 15 minutes.