diff options
| author |  Nicolas Noble <nicolasnoble@users.noreply.github.com> | 2016-07-01 17:24:44 -0700 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2016-07-01 17:24:44 -0700 |
| commit | 77e8b714e510c6a3061d17aab8af769a7b45eed4 (patch) | |
| tree | 33048c1cb7b6c20de3638a899dab985d76b58b28 /doc | |
| parent | 123a1b76d30f47527774d878f9e0e6cb30f4fb83 (diff) | |
| parent | eda85c6765bf9b201fe5fa3185b704490f14026e (diff) | |
Merge pull request #7210 from ctiller/no-more-zookeeper
Expunge all references to zookeeper
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/naming.md | 22 |
1 files changed, 0 insertions, 22 deletions
diff --git a/doc/naming.md b/doc/naming.md index 5ad7e6622e..d0c892e8d9 100644 --- a/doc/naming.md +++ b/doc/naming.md @@ -16,8 +16,6 @@ Here, scheme indicates the name-system to be used. Example schemes to be support * `dns` -* `zookeeper` - * `etcd` Authority indicates some scheme-specific bootstrap information, e.g., for DNS, the authority may include the IP[:port] of the DNS server to use. Often, a DNS name may used as the authority, since the ability to resolve DNS names is already built into all gRPC client libraries. @@ -30,23 +28,3 @@ The gRPC client library will switch on the scheme to pick the right resolver plu Resolvers should be able to contact the authority and get a resolution that they return back to the gRPC client library. The returned contents include a list of IP:port, an optional config and optional auth config data to be used for channel authentication. The plugin API allows the resolvers to continuously watch an endpoint_name and return updated resolutions as needed. -## Zookeeper - -Apache [ZooKeeper](https://zookeeper.apache.org/) is a popular solution for building name-systems. Curator is a service discovery system built on to of ZooKeeper. We propose to organize names hierarchically as `/path/service/instance` similar to Apache Curator. - -A fully-qualified ZooKeeper name used to construct a gRPC channel will look as follows: - -``` -zookeeper://host:port/path/service/instance -``` -Here `zookeeper` is the scheme identifying the name-system. `host:port` identifies an authoritative name-server for this scheme (i.e., a Zookeeper server). The host can be an IP address or a DNS name. -Finally `/path/service/instance` is the Zookeeper name to be resolved. - -## Service Registration - - -Service providers can register their services in Zookeeper by using a Zookeeper client. - -Each service is a zookeeper node, and each instance is a child node of the corresponding service. For example, a MySQL service may have multiple instances, `/mysql/1`, `/mysql/2`, `/mysql/3`. The name of the service or instance, as well as an optional path is specified by the service provider. - -The data in service nodes is empty. Each instance node stores its address in the format of `host:port`, where host can be either hostname or IP address. |