rosstimothy b8394b3bd3 Prevent relative expiry from emitting more events than can be processed (#12002) ...

* Prevent relative expiry from emitting more events than can be processed

This alters relative expiry in four ways:

1) Relative expiry is no longer exclusively run by the auth cache
2) Relative expiry no longer emits delete events
3) There is now a limit to the number of nodes removed per interval
4) Relative expiry now runs more frequently

We can remove the need to emit any fake delete events during relative
expiry by not running it exclusively in the auth cache. All caches
will now run relative expiry themselves, even the components that
don't watch for nodes - this is effectively a noop for them. To
prevent the individual caches from getting too far out of sync, the
expiry interval is set to a much smaller value and we limit the
number of nodes being deleted per interval.

2022-04-25 13:22:27 +00:00

..

interval_test.go

Prevent relative expiry from emitting more events than can be processed (#12002)

2022-04-25 13:22:27 +00:00

interval.go

Prevent relative expiry from emitting more events than can be processed (#12002)

2022-04-25 13:22:27 +00:00