Skip to content
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

Informers should timeout if initial sync blocks forever #654

Closed
mattmoyer opened this issue Jun 1, 2021 · 0 comments · Fixed by #829
Closed

Informers should timeout if initial sync blocks forever #654

mattmoyer opened this issue Jun 1, 2021 · 0 comments · Fixed by #829
Assignees
Labels
chore Not a bug or an enhancement, but still a work item state/accepted All done!

Comments

@mattmoyer
Copy link
Contributor

We should consider rebasing the change from #137. This would adjust our startup flow to include a long timeout (10 minutes?) instead of blocking forever to wait for the all the informers to finish their initial sync.

We haven't observed any negative consequences of the current flow, but a timeout would be easier to diagnose/debug.

@pinniped-ci-bot pinniped-ci-bot added enhancement New feature or request priority/undecided Not yet prioritized chore Not a bug or an enhancement, but still a work item and removed enhancement New feature or request labels Jun 1, 2021
@pinniped-ci-bot pinniped-ci-bot added priority/backlog Prioritized for an upcoming iteration state/started Someone is working on it currently state/accepted All done! and removed priority/undecided Not yet prioritized priority/backlog Prioritized for an upcoming iteration state/started Someone is working on it currently labels Sep 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Not a bug or an enhancement, but still a work item state/accepted All done!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants