Ensure that the retry policy for your Cloud Tasks queue includes an exponential backoff configuration in order to reduce the risk of overwhelming downstream services during failures. In Cloud Tasks, a task will be retried after a failure within the duration specified by the "minBackoff" and "maxBackoff" parameters. Before running this conformity rule, ensure the "minBackoff" and "maxBackoff" parameters are set in the Trend Cloud One™ – Conformity account settings for exponential backoff.
efficiency
Exponential backoff for retries in Google Cloud Tasks queues increases the delay between retry attempts after each failure. Setting "minBackoff" and "maxBackoff" flags is important to control the minimum and maximum retry intervals. "minBackoff" sets the initial delay, while "maxBackoff" sets the upper limit, preventing excessive delays and ensuring eventual retry termination. This strategy prevents overwhelming failing services and allows for temporary recovery.
Audit
To determine if exponential backoff for retries is configured for your Google Cloud Tasks queues, perform the following operations:
Remediation / Resolution
To ensure that the retry policy defined for your Google Cloud Tasks queues includes a compliant, exponential backoff configuration, perform the following operations:
References
- Google Cloud Platform (GCP) Documentation
- Understand Cloud Tasks
- Configure Cloud Tasks queues
- GCP Command Line Interface (CLI) Documentation
- gcloud projects list
- gcloud tasks queues list
- gcloud tasks queues describe
- gcloud tasks queues update