Struct google_cloudtasks2_beta2::RetryConfig [−][src]
pub struct RetryConfig {
pub max_attempts: Option<i32>,
pub max_retry_duration: Option<String>,
pub min_backoff: Option<String>,
pub max_doublings: Option<i32>,
pub max_backoff: Option<String>,
pub unlimited_attempts: Option<bool>,
}Retry config.
These settings determine how a failed task attempt is retried.
This type is not used in any activity, and only used as part of another schema.
Fields
max_attempts: Option<i32>
The maximum number of attempts for a task.
Cloud Tasks will attempt the task max_attempts times (that
is, if the first attempt fails, then there will be
max_attempts - 1 retries). Must be > 0.
max_retry_duration: Option<String>
If positive, max_retry_duration specifies the time limit for retrying a
failed task, measured from when the task was first attempted. Once
max_retry_duration time has passed and the task has been attempted
RetryConfig.max_attempts times, no further attempts will be made and
the task will be deleted.
If zero, then the task age is unlimited.
- For App Engine queues, this field is 0 seconds by default.
- For pull queues, this field is output only and always 0.
max_retry_duration will be truncated to the nearest second.
This field has the same meaning as task_age_limit in queue.yaml.
min_backoff: Option<String>
The minimum amount of time to wait before retrying a task after it fails.
- For App Engine queues, this field is 0.1 seconds by default.
- For pull queues, this field is output only and always 0.
min_backoff will be truncated to the nearest second.
This field has the same meaning as min_backoff_seconds in queue.yaml.
max_doublings: Option<i32>
The time between retries will double max_doublings times.
A task's retry interval starts at RetryConfig.min_backoff,
then doubles max_doublings times, then increases linearly, and
finally retries retries at intervals of
RetryConfig.max_backoff up to max_attempts times.
For example, if RetryConfig.min_backoff is 10s,
RetryConfig.max_backoff is 300s, and max_doublings is 3,
then the a task will first be retried in 10s. The retry interval
will double three times, and then increase linearly by 2^3 * 10s.
Finally, the task will retry at intervals of
RetryConfig.max_backoff until the task has been attempted
max_attempts times. Thus, the requests will retry at 10s, 20s,
40s, 80s, 160s, 240s, 300s, 300s, ....
- For App Engine queues, this field is 16 by default.
- For pull queues, this field is output only and always 0.
This field has the same meaning as max_doublings in queue.yaml.
max_backoff: Option<String>
The maximum amount of time to wait before retrying a task after it fails. The default is 1 hour.
- For App Engine queues, this field is 1 hour by default.
- For pull queues, this field is output only and always 0.
max_backoff will be truncated to the nearest second.
This field has the same meaning as max_backoff_seconds in queue.yaml.
unlimited_attempts: Option<bool>
If true, then the number of attempts is unlimited.
Trait Implementations
impl Default for RetryConfig[src]
impl Default for RetryConfigfn default() -> RetryConfig[src]
fn default() -> RetryConfigReturns the "default value" for a type. Read more
impl Clone for RetryConfig[src]
impl Clone for RetryConfigfn clone(&self) -> RetryConfig[src]
fn clone(&self) -> RetryConfigReturns a copy of the value. Read more
fn clone_from(&mut self, source: &Self)1.0.0[src]
fn clone_from(&mut self, source: &Self)Performs copy-assignment from source. Read more
impl Debug for RetryConfig[src]
impl Debug for RetryConfigfn fmt(&self, f: &mut Formatter) -> Result[src]
fn fmt(&self, f: &mut Formatter) -> ResultFormats the value using the given formatter. Read more
impl Part for RetryConfig[src]
impl Part for RetryConfigAuto Trait Implementations
impl Send for RetryConfig
impl Send for RetryConfigimpl Sync for RetryConfig
impl Sync for RetryConfig