Skip to content

NimTechnology

Trình bày các công nghệ CLOUD một cách dễ hiểu.

  • Kubernetes & Container
    • Docker
    • Kubernetes
      • Ingress
      • Pod
    • Helm Chart
    • OAuth2 Proxy
    • Isito-EnvoyFilter
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Vault
    • Longhorn – Storage
    • VictoriaMetrics
    • MetalLB
    • Kong Gateway
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Argo Events
    • Spinnaker
    • Jenkins
    • Harbor
    • TeamCity
    • Git
      • Bitbucket
  • Coding
    • DevSecOps
    • Terraform
      • GCP – Google Cloud
      • AWS – Amazon Web Service
      • Azure Cloud
    • Golang
    • Laravel
    • Python
    • Jquery & JavaScript
    • Selenium
  • Log, Monitor & Tracing
    • DataDog
    • Prometheus
    • Grafana
    • ELK
      • Kibana
      • Logstash
  • BareMetal
    • NextCloud
  • Toggle search form

[Argo-Workflows] Lesson17: Retry strategy

Posted on April 11, 2023April 11, 2023 By nim No Comments on [Argo-Workflows] Lesson17: Retry strategy

Khi một task bị fail thì chúng ta sẽ cần phải retry lại task đó 1 vài lần.
chẳng hạn, như bạn connect vào Database nếu không được thì bạn sẽ muốn retry lại.

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: wf-retrystrategy-
spec:
  entrypoint: dag-template
  arguments:
    parameters:
    - name: messageA
      value: A

  templates:
  - name: dag-template
    inputs:
      parameters:
      - name: messageA
    dag:
      tasks:
      - name: Task1
        arguments:
          parameters: [{name: text, value: "{{inputs.parameters.messageA}}"}]
        template: task-decision
      - name: TaskA
        template: task-a
        depends: Task1.Succeeded
        when: "{{tasks.Task1.outputs.result}} == A"


  - name: task-decision
    inputs:
      parameters: 
      - name: text
    script:
      image: python:3.8-slim
      command: 
      source: |
        p = "{{inputs.parameters.text}}"
        print(p)

  - name: task-a
    retryStrategy:
      limit: 10
      retryPolicy: "Always"
      backoff:
        duration: "1"
        factor: 2
        maxiDuration: "1m"
    script:
      image: python:3.8-slim
      command: 
      source: |
        print("Task A was executed)


Certainly! The retryStrategy section in your Argo Workflow task definition specifies how many times the task will be retried if it fails and how the retries will be spaced out.

Here’s a breakdown of the different parameters:

  • limit: This parameter specifies how many times the task will be retried before giving up. In this case, the limit is set to 2, which means that the task will be executed up to 3 times in total (the initial attempt plus two retries).
  • retryPolicy: This parameter specifies when the task should be retried. In this case, the value is set to “Always”, which means that the task will be retried regardless of the reason for the failure (e.g., a network error or a syntax error in the script).
  • backoff: This parameter specifies how the retries will be spaced out. Specifically, it defines the duration of each retry attempt, the factor by which the duration will increase with each subsequent retry, and the maximum duration for any single retry.
    • duration: This parameter specifies the initial duration for the first retry attempt. In this case, the duration is set to “1”, which means that the first retry attempt will be executed after a one-second delay.
    • factor: This parameter specifies the multiplier used to calculate the duration of each subsequent retry attempt. In this case, the factor is set to 2, which means that the duration of each subsequent retry attempt will be double the duration of the previous attempt.
    • maxDuration: This parameter specifies the maximum duration for any single retry attempt. In this case, the maximum duration is set to “1m”, which means that the duration of each retry attempt will not exceed one minute.

Together, these parameters define a retry strategy that will attempt to execute the task up to 3 times, with each retry attempt spaced out by an exponentially increasing delay, up to a maximum of one minute per retry. This strategy can be useful in scenarios where the task may encounter intermittent errors, network issues or where the task’s environment may not be stable or consistent.

Bạn sẽ thấy là tổng duration sẽ không lớn hơn 1 phút vì mình đang set maxiDuration: “1m”
ArgoWorkflows

Post navigation

Previous Post: [Argo-Workflows] Lesson16: Depends
Next Post: [Argo-Workflows] Lesson18: Recursion

More Related Articles

[Argo Workflow] Build the docker image with argo-workflow and Kaniko then push the image to ECR ArgoWorkflows
[Argo-Workflows] Lesson23: Creating a Master Workflow ArgoWorkflows
[Argo-Workflows] Lesson16: Depends ArgoWorkflows
[Argo-Workflows] Lesson18: Recursion ArgoWorkflows
[Argo-Workflows] Lesson11: Loops with sets ArgoWorkflows
[Argo Workflow] Run in a test case Using a sidecar or two containers together. ArgoWorkflows

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Tham Gia Group DevOps nhé!
Để Nim có nhiều động lực ra nhiều bài viết.
Để nhận được những thông báo mới nhất.

Recent Posts

  • [Laravel] Laravel Helpful June 26, 2025
  • [VScode] Hướng dẫn điều chỉnh font cho terminal June 20, 2025
  • [WordPress] Hướng dấn gửi mail trên WordPress thông qua gmail. June 15, 2025
  • [Bitbucket] Git Clone/Pull/Push with Bitbucket through API Token. June 12, 2025
  • [Teamcity] How to transfer the value from pipeline A to pipeline B June 9, 2025

Archives

  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021

Categories

  • BareMetal
    • NextCloud
  • CI/CD
    • Argo Events
    • ArgoCD
    • ArgoWorkflows
    • Git
      • Bitbucket
    • Harbor
    • Jenkins
    • Spinnaker
    • TeamCity
  • Coding
    • DevSecOps
    • Golang
    • Jquery & JavaScript
    • Laravel
    • NextJS 14 & ReactJS & Type Script
    • Python
    • Selenium
    • Terraform
      • AWS – Amazon Web Service
      • Azure Cloud
      • GCP – Google Cloud
  • Kubernetes & Container
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Docker
    • Helm Chart
    • Isito-EnvoyFilter
    • Kong Gateway
    • Kubernetes
      • Ingress
      • Pod
    • Longhorn – Storage
    • MetalLB
    • OAuth2 Proxy
    • Vault
    • VictoriaMetrics
  • Log, Monitor & Tracing
    • DataDog
    • ELK
      • Kibana
      • Logstash
    • Fluent
    • Grafana
    • Prometheus
  • Uncategorized
  • Admin

Copyright © 2025 NimTechnology.