You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/06/17 05:58:34 UTC

[GitHub] [apisix] SylviaBABY commented on a diff in pull request #7270: docs(zookeeper): move zookeeper doc to apisix-seed

SylviaBABY commented on code in PR #7270:
URL: https://github.com/apache/apisix/pull/7270#discussion_r899787367


##########
docs/en/latest/discovery/zookeeper.md:
##########
@@ -21,124 +21,4 @@ title: zookeeper
 #
 -->
 
-## Service Discovery Via Zookeeper
-
-`Zookeeper` service discovery needs to rely on the [apisix-seed](https://github.com/api7/apisix-seed) project.
-
-### How `apisix-seed` Works
-
-![APISIX-SEED](../../../assets/images/apisix-seed.svg)
-
-`apisix-seed` completes data exchange by watching the changes of `etcd` and `zookeeper` at the same time.
-
-The process is as follows:
-
-1. `APISIX` registers an upstream and specifies the service discovery type as `zookeeper` to `etcd`.
-2. `apisix-seed` watches the resource changes of `APISIX` in `etcd` and filters the discovery type and obtains the service name.
-3. `apisix-seed` binds the service to the `etcd` resource and starts watching the service in zookeeper.
-4. The client registers the service with `zookeeper`.
-5. `apisix-seed` gets the service changes in `zookeeper`.
-6. `apisix-seed` queries the bound `etcd` resource information through the service name, and writes the updated service node to `etcd`.
-7. The `APISIX` worker watches `etcd` changes and refreshes the service node information to the memory.
-

Review Comment:
   I think this part should be kept



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org