-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Context deadline exceeded when having more than 30 apps #1641
Comments
I'm almost sure this is because of this change #1528 @peterbosalliandercom , do you store all applications in a single repo? In this case repo server responses might be slow because it hold lock per repo during manifest generation. As a quick fix you can increase timeout using '--repo-server-timeout-seconds' flag in argocd-application-controller deployment. By default it is 60 seconds |
You can also increase number of repo servers to improve performance. Meanwhile we should optimize template generation in case when repo has a lots of applications. |
We will test thism thanks for quick response |
@peterbosalliandercom did you have a chance to check if '--repo-server-timeout-seconds' helps? |
We were facing the same issue. This helped instantly. apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-application-controller
spec:
template:
spec:
containers:
- name: argocd-application-controller
command:
- argocd-application-controller
- --status-processors
- "20"
- --operation-processors
- "10"
- --repo-server-timeout-seconds
- "180" |
Looks fine with these settings. I am wondering what the other settings do, the status processors and operation processors |
Thanks for confirming! The |
Describe the bug
with version 1.0.0
When using more than 20 apps it appears a lot of the time that argo cannot refresh or sync and gives context deadline exceeded errors.
To Reproduce
Use more applications and the problem appears
Expected behavior
Quick response without errors
Screenshots
If applicable, add screenshots to help explain your problem.
Version
Logs
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: