summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChao Xu <xuchao@google.com>2016-02-24 10:41:16 -0800
committerChao Xu <xuchao@google.com>2016-02-29 13:27:29 -0800
commit87e88066dfe295c78bdec1706a1a64bb742c8239 (patch)
treed88b5ea052acd28bbdfb0ba5c103d083c8a38c7e
parentd4a1d08cfc63e9de357ae503a4676a6436c9f354 (diff)
fix links
-rw-r--r--event_compression.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/event_compression.md b/event_compression.md
index c8030559..3a05db21 100644
--- a/event_compression.md
+++ b/event_compression.md
@@ -100,7 +100,7 @@ Each binary that generates events:
* `event.Reason`
* `event.Message`
* The LRU cache is capped at 4096 events for both `EventAggregator` and `EventLogger`. That means if a component (e.g. kubelet) runs for a long period 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/unversioned/record/event.go)).
+ * 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)).
* 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 the existing event entry is updated in etcd:
* The new PUT (update) event API is called to update the existing event entry in etcd with the new last seen timestamp and count.
* The event is also updated in the previously generated events cache with an incremented count, updated last seen timestamp, name, and new resource version (all required to issue a future event update).