Will that affect the existing ZK metadata in a pulsar instance , When we upgrade from a lower version to 2.10 ? In other words, Do we need a metadate migration to switch from ZK to Etcd ?
Thanks Tamer On Fri, 14 Jan 2022, 22:52 Matteo Merli, <[email protected]> wrote: > https://github.com/apache/pulsar/issues/13717 > > ----- > > ## Motivation > > Since all the pieces that composed the proposal in PIP-45 were finally > merged > and are currently ready for 2.10 release, it is now possible to add other > metadata backends that can be used to support a BookKeeper + Pulsar > cluster. > > One of the popular systems that is most commonly used as an alternative of > ZooKeeper is Etcd, thus it makes sense to have this as the first > non-zookeeper > implementation. > > ## Goal > > Provide an Etcd implementation for the `MetadataStore` API. This will allow > users to deploy Pulsar clusters using Etcd service for the metadata and it > will > not require the presence of ZooKeeper. > > > ## Implementation > > * Use the existing JEtcd Java client library for Etcd > * Extends the `AbstractBatchedMetadataStore` class, in order to reuse the > transparent batching logic that will be shared with the ZooKeeper > implementation. > > Work in progress: https://github.com/apache/pulsar/pull/13225 > > -- > Matteo Merli > <[email protected]> >
