Mike Danese ba0da5aa4d NewIndexerInformerWatcher: fix goroutine leak ...

There was some weird queuing going on. The queue was implement by
spawning goroutines that would block on the "ticketer" until it was
their turn to write to the output channel. If N events where in the
watch when the consumer of the watch stopped reading events, N
goroutines would leak. In unit tests of the certificate manager, this
was causing ~10k goroutines to leak.

Fix it with a buffering event processor that uses only one routine and
cancels correctly.

Kubernetes-commit: cafc640bfa0f7362b178b1b896085962d018afe3

2019-05-03 23:50:53 -04:00

..

informerwatcher_test.go

NewIndexerInformerWatcher: fix goroutine leak

2019-05-03 23:50:53 -04:00

informerwatcher.go

NewIndexerInformerWatcher: fix goroutine leak

2019-05-03 23:50:53 -04:00

retrywatcher_test.go

Fix race in RetryWatcher's unit tests

2019-02-27 16:35:55 +01:00

retrywatcher.go

add watch bookmark

2019-03-19 18:16:23 +08:00

until_test.go

Call cancel functions to avoid context leaks

2018-11-18 17:40:35 +08:00

until.go

Upgrade ListWatchUntil

2019-02-18 18:20:23 +01:00