scottk/kubernetes
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/kubernetes.git synced 2025-11-04 04:08:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #19278 from philips/minor-edits-to-apiserver-watch-scaling

Browse Source 
docs: apiserver-watch: minor cleanups
This commit is contained in:
Mike Danese
2016-01-14 11:51:48 -08:00
parent 5b270551a9 dc8d8371aa
commit b3d035e16f
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -34,9 +34,9 @@ Documentation for other releases can be found at
## Abstract ## Abstract
In the current system, all watch requests send to apiserver are in general In the current system, most watch requests sent to apiserver are redirected to
redirected to etcd. This means that for every watch request to apiserver, etcd. This means that for every watch request the apiserver opens a watch on
apiserver opens a watch on etcd. etcd.
The purpose of the proposal is to improve the overall performance of the system The purpose of the proposal is to improve the overall performance of the system
by solving the following problems: by solving the following problems:
@@ -99,7 +99,7 @@ to implement the proposal.
1. Since we want the watch in apiserver to be optional for different resource 1. Since we want the watch in apiserver to be optional for different resource
types, this needs to be self-contained and hidden behind a well defined API. types, this needs to be self-contained and hidden behind a well defined API.
This should be a layer very close to etcd - in particular all registries: This should be a layer very close to etcd - in particular all registries:
"pkg/registry/generic/etcd" should be build on top of it. "pkg/registry/generic/etcd" should be built on top of it.
We will solve it by turning tools.EtcdHelper by extracting its interface We will solve it by turning tools.EtcdHelper by extracting its interface
and treating this interface as this API - the whole watch mechanisms in and treating this interface as this API - the whole watch mechanisms in
apiserver will be hidden behind that interface. apiserver will be hidden behind that interface.