You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present, reconcile.Reconciler allows multiple concurrent reconciliations through adjustment of the MaxConcurrentReconciles property to values above 1. However, this opens the possibility that there could be two concurrent reconciliations for the same resource, which is a situation we would like to avoid.
We would like to be able to configure the Reconciler so that it supports concurrent reconciliations only for distinct resources. In other words, it would be possible to concurrently reconcile resources A and B, but not to have two concurrent reconciliations for either A or B.
The text was updated successfully, but these errors were encountered:
This shouldn't happen -- the underlying workqueue should prevent this from occurring (see the bullet item for "stingy" in https://godoc.org/k8s.io/client-go/util/workqueue). Do you see this actually occurring?
@DirectXMan12 thanks for pointing that out!
You were right, the reconciler internal queue prevents concurrent updates for the same resource name, but still allows concurrent updates for different resources when MaxConcurrentReconciles is greater than 1.
At present,
reconcile.Reconciler
allows multiple concurrent reconciliations through adjustment of theMaxConcurrentReconciles
property to values above 1. However, this opens the possibility that there could be two concurrent reconciliations for the same resource, which is a situation we would like to avoid.We would like to be able to configure the
Reconciler
so that it supports concurrent reconciliations only for distinct resources. In other words, it would be possible to concurrently reconcile resources A and B, but not to have two concurrent reconciliations for either A or B.The text was updated successfully, but these errors were encountered: