Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

readme.md update etcd v2 and v3 description #317

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -323,6 +323,15 @@ or
Etcd_interface
======

**crucial**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

想了下,放在这里感觉有点不合适,这里只是介绍接口使用方式,而且v2、v3 在这里是一致的;
应该放在Compatibility 下?当前这个标题下只涉及了nginx 的兼容性,consul 和 etcd 的都没涉及,能帮忙在这个标题下面加三个二级标题吗?nginx、consul、etcd,其中nginx 就是当前的内容,consul 支持v1 版本,etcd 支持v2、v3,但是v3 需要etcdv3_upsync_proxy[https://github.com/reatang/etcdv3_upsync_proxy] 的代理才可以work;
类似上面的结构,你觉得咋样?谢谢.


etcd's http_interface v2 and v3 are completely incompatible. To enable v2 on v3, you need to enter `--enable-v2=true` or ENV `ETCD_ENABLE_V2=true`. In addition, data submitted by grpc clients using version v3 is not visible in version v2, and they are separated from the storage layer.

If you must use it in the etcd v3 storage, can refer to an open source external to implement proxy:
https://github.com/reatang/etcdv3_upsync_proxy

**etcd v2 http_interface**

you can add or delete backend server through http_interface.

mainly like etcd, http_interface example:
Expand Down