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
{{ message }}
This repository has been archived by the owner on May 6, 2022. It is now read-only.
While preparing the Kubecon demo, I found that the controller can get into a state where new resources are not worked on. The scenario I ran into is:
I had added several brokers to the catalog, some of which were deployed into the same cluster as the catalog itself. Currently the controller has a resync period for all informers hard-coded to 1 minute. When those brokers went sideways for whatever reason, they would time out when the controller tried to contact them. Due to those timeouts, the resync interval would elapse before the controller had time to work on the new resources.
There are a few different facets of this situation that need improvement; I'm going to create issues for them because focused issues are more easy to track, but wanted to tie them together here.
While preparing the Kubecon demo, I found that the controller can get into a state where new resources are not worked on. The scenario I ran into is:
I had added several brokers to the catalog, some of which were deployed into the same cluster as the catalog itself. Currently the controller has a resync period for all informers hard-coded to 1 minute. When those brokers went sideways for whatever reason, they would time out when the controller tried to contact them. Due to those timeouts, the resync interval would elapse before the controller had time to work on the new resources.
There are a few different facets of this situation that need improvement; I'm going to create issues for them because focused issues are more easy to track, but wanted to tie them together here.
TLDR:
The text was updated successfully, but these errors were encountered: