How can I configure sync timeout?

[smeeklai]

I deployed ArgoCD via Helm and I want to configure ArgoCD sync timeout because whenever there's an error occurred, ArgoCD retries and wait for a bit too long until I got sync failure notification.

[jgwest]

Hi @smeeklai,

There's no way to set a 'maximum time/expiration time' on the sync operation AFAICT, but you can configure the number of retries...

When creating an application (for example, via the CLI), the number of retries (and the time between retries) can be configured:

      --sync-policy string                         Set the sync policy (one of: none, automated (aliases of automated: auto, automatic))
      --sync-retry-backoff-duration duration       Sync retry backoff base duration. Input needs to be a duration (e.g. 2m, 1h) (default 5s)
      --sync-retry-backoff-factor int              Factor multiplies the base duration after each failed sync retry (default 2)
      --sync-retry-backoff-max-duration duration   Max sync retry backoff duration. Input needs to be a duration (e.g. 2m, 1h) (default 3m0s)
      --sync-retry-limit int                       Max number of allowed sync retries

(https://argoproj.github.io/argo-cd/user-guide/commands/argocd_app_create/)

Primarily for your question you would want to look at --sync-retry-limit.

Or you can add/tweak the same options on the Application CR:

argo-cd/docs/operator-manual/application.yaml

Line 111 in ac2491d

retry:

For example:

    retry:
      limit: 1 # number of failed sync attempt retries; unlimited number of attempts if less than 0

[smeeklai]

Understood. Thank you :)

[benedikt-haug]

I would absolutely love a timeout for sync operations. Currently I have to manually track and cancel jobs that couldn't complete.

[melch]

We have a similar experience. Setting the max number of retries doesn't help our system because a single sync attempt can get stuck and never complete, so we won't hit a max number of retries.

[thapakazi]

[brat002]

Any progress or plans to include the feature into upcomming release? really annoying... :( Probably retry option doesn't work as expected.

[riuvshyn]

still no sync timeout???

[hellojanam]

we are facing this issue too, if we deployed something and that caused pods to crash then the sync never stops, which caused issue. we love to have sync time out.

[richardfelkl]

The sync timeout would be very much appreciated.

[erikschul]

Why is this a discussion instead of an issue?

Possibly related:
#15642

[aslafy-z]

I think this is the original issue #11494 and this the original discussion #11276

[riuvshyn]

Sync timeout is a must... there are too many things that might go wrong and result into a never ending sync that would last forever which atm require manual intervention. :/

[sudeepgupta90]

Using argocd_app_info{sync_status="OutOfSync"}>=1 for 30 min to detect such scenarios. It doesn't fix this problem, but at least gives visibility from metrics side on Prometheus

[keskad]

In my case hanging Post-Sync jobs are causing e.g. 15 hours running synchronization. Timeout would be nice.

[szczepq]

We have a similar problem. One of ArgoCD is installed on a VM that we don't have access to so when we make a mistake and even fix it in the next commit we can't manually terminate the current ongoing sync and re-run the new one with the fix. ;/

[jeevanions]

This is big issues for us where we had to manually go through large number of ArgoCD apps and terminate the ongoing sync and re-sync. We would like some configurable parameters to play with around timeout.

[aslafy-z]

Please check #11494
I'm waiting for feedback for a PR that would solve this issue

[greenkiwi]

We have also been having some issues where having a sync timeout would be very useful. Changes just get stuck in a syncing state and never progress or fail. Then the changes to fix the issue aren't able to sync.

[JavierPorron]

I'm facing many issues because of this... would be lovely to have a sync timeout

[rumstead]

As of Argo CD v2.14, a global sync timeout can be configured for applications.
https://blog.argoproj.io/argo-cd-v2-14-release-candidate-57a664791e2a

The global sync timeout feature addresses issues where the sync process gets stuck indefinitely, often due to resources failing to start properly and continuously retrying. Now, a global timeout can be configured on the Argo CD Controller to timeout long-running sync operations thanks to Andrii Korotkov (Verkada)!

You can configure the timeout by updating controller.sync.timeout.seconds in the argocd-cmd-params-cm configmap.