github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-04 18:00:08 +00:00
Code Issues Projects Releases Wiki Activity

Manually fixing docs, since gendocs messes up the links.

Browse Source
This commit is contained in:
Daniel Smith 2015-09-03 14:50:12 -07:00
parent b225c1d47a
commit 82d6489556
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/design/event_compression.md
View File

@ -60,7 +60,7 @@ Instead of a single Timestamp, each event object [contains](http://releases.k8s.
Each binary that generates events: Each binary that generates events:
* Maintains a historical record of previously generated 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/unversioned/record/events_cache.go`](../../pkg/client/unversioned/record/events_cache.go). * 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).
* The key in the cache is generated from the event object minus timestamps/count/transient fields, specifically the following events fields are used to construct a unique key for an event: * The key in the cache is generated from the event object minus timestamps/count/transient fields, specifically the following events fields are used to construct a unique key for an event:
* `event.Source.Component` * `event.Source.Component`
* `event.Source.Host` * `event.Source.Host`

2
docs/proposals/apiserver-watch.md
View File

@ -166,7 +166,7 @@ the same time, we can introduce an additional etcd event type:
Thus, we need to create the EtcdResync event, extend watch.Interface and Thus, we need to create the EtcdResync event, extend watch.Interface and
its implementations to support it and handle those events appropriately its implementations to support it and handle those events appropriately
in places like in places like
[Reflector](../../pkg/client/unversioned/cache/reflector.go) [Reflector](../../pkg/client/cache/reflector.go)
However, this might turn out to be unnecessary optimization if apiserver However, this might turn out to be unnecessary optimization if apiserver
will always keep up (which is possible in the new design). We will work will always keep up (which is possible in the new design). We will work