Thank you Yuansheng for creating this discussion thread! I wonder if it possible that some of the users would need "online migration", which "an etcd downtime window spanning from seconds to minutes" for them is not acceptable.
If true, then maybe we need to publish a release that supports both etcd protocols for the online migration, and then publish releases that only support v3. Ming Wen <[email protected]> 于2020年8月18日周二 上午11:13写道： > +1. > etcd v2 is a protocol that will be officially discontinued by etcd. We > should migrate to etcd v3 as soon as possible. > And the data migration from etcd v2 to v3 is a relatively incompatible > modification. > I agree to change the next release version number of Apache APISIX to 2.0. > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing > > > YuanSheng Wang <[email protected]> 于2020年8月18日周二 上午11:00写道： > > > Hi: > > > > Support etcd v3 is on the way, here is the PR [1], it'll be merged soon. > > > > I think we can support etcd v3 ONLY. The users can follow doc [2], > migrate > > application data from `v2` to `v3`. > > > > Since the v3 and v2 versions of etcd are quite different, I think we can > > use `2.0` version, > > changing the major version makes it easier for users to pay attention to > > the difference. > > > > [1] https://github.com/apache/apisix/pull/2036 > > [2] > > > > > https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/v2-migration.md > > > > -- > > > > *MembPhis* > > My GitHub: https://github.com/membphis > > Apache APISIX: https://github.com/apache/incubator-apisix > > >
