diff options
| author | XsWack <xushiwei5@huawei.com> | 2017-08-23 21:15:31 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-08-23 21:15:31 +0800 |
| commit | ce2e4e37672d2928f9453a92eb7d7f68086bc178 (patch) | |
| tree | f2644a1ae250c03615d4ea800bc19ad38ca76174 | |
| parent | 0150dd4d008ca96dedaa456e060afb9415d96a4e (diff) | |
Update event_compression.md
fix bad url
| -rw-r--r-- | contributors/design-proposals/event_compression.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/contributors/design-proposals/event_compression.md b/contributors/design-proposals/event_compression.md index 7a1cbb33..e041affe 100644 --- a/contributors/design-proposals/event_compression.md +++ b/contributors/design-proposals/event_compression.md @@ -53,7 +53,7 @@ Each binary that generates events: * Maintains a historical record of previously generated events: * Implemented with ["Least Recently Used Cache"](https://github.com/golang/groupcache/blob/master/lru/lru.go) -in [`pkg/client/record/events_cache.go`](../../pkg/client/record/events_cache.go). +in [`pkg/client/record/events_cache.go`](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/tools/record/events_cache.go). * Implemented behind an `EventCorrelator` that manages two subcomponents: `EventAggregator` and `EventLogger`. * The `EventCorrelator` observes all incoming events and lets each @@ -98,7 +98,7 @@ of time and generates tons of unique events, the previously generated events cache will not grow unchecked in memory. Instead, after 4096 unique events are generated, the oldest events are evicted from the cache. * When an event is generated, the previously generated events cache is checked -(see [`pkg/client/unversioned/record/event.go`](http://releases.k8s.io/HEAD/pkg/client/record/event.go)). +(see [`pkg/client/unversioned/record/event.go`](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/tools/record/event.go)). * If the key for the new event matches the key for a previously generated event (meaning all of the above fields match between the new event and some previously generated event), then the event is considered to be a duplicate and |