Task Retry Policy is implemented on a best-effort basis. Retry delay
will be exponential based on provided minimum and maximum backoffs.
https://en.wikipedia.org/wiki/Exponential_backoff. Note that the
delay between consecutive task restarts may not always precisely
match the configured settings. This can happen when the
ConnectCluster is in rebalancing state or if the ConnectCluster is
unresponsive etc. The default values for minimum and maximum
backoffs are 60 seconds and 30 minutes respectively.
Attributes
Name
Description
minimum_backoff
google.protobuf.duration_pb2.Duration
Optional. The minimum amount of time to wait
before retrying a failed task. This sets a lower
bound for the backoff delay.
maximum_backoff
google.protobuf.duration_pb2.Duration
Optional. The maximum amount of time to wait
before retrying a failed task. This sets an
upper bound for the backoff delay.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[],null,["# Class TaskRetryPolicy (0.1.12)\n\nVersion latestkeyboard_arrow_down\n\n- [0.1.12 (latest)](/python/docs/reference/google-cloud-managedkafka/latest/google.cloud.managedkafka_v1.types.TaskRetryPolicy)\n- [0.1.11](/python/docs/reference/google-cloud-managedkafka/0.1.11/google.cloud.managedkafka_v1.types.TaskRetryPolicy) \n\n TaskRetryPolicy(mapping=None, *, ignore_unknown_fields=False, **kwargs)\n\nTask Retry Policy is implemented on a best-effort basis. Retry delay\nwill be exponential based on provided minimum and maximum backoffs.\n\u003chttps://en.wikipedia.org/wiki/Exponential_backoff\u003e. Note that the\ndelay between consecutive task restarts may not always precisely\nmatch the configured settings. This can happen when the\nConnectCluster is in rebalancing state or if the ConnectCluster is\nunresponsive etc. The default values for minimum and maximum\nbackoffs are 60 seconds and 30 minutes respectively."]]
