On Fri, Apr 17, 2020 at 4:57 AM Subash K <[email protected]> wrote:
> Hi, > > > > We are evaluating Apache Pulsar to be integrated with our product and > currently we are trying to understand the Life Cycle Management of the > Pulsar components. So I would like to get the following points clarified: > > > > - We see that, Bookkeeper is packed and delivered by Pulsar. As part > of Pulsar 2.5.0, the provided Bookkeeper version is 4.10.0. May I please > know the strategy on how the bookkeeper version are planned to be upgraded > for each release of Pulsar? > - From Apache Bookkeeper page, I understand that the stable version > is 4.9.2, but Pulsar 2.5.0 has deployed 4.10.0. Can I assume that Pulsar > always delivers the latest version of Apache Bookkeeper irrespective of > stable build? > > I think the bookkeeper website is not updated with the latest stable version. Most of the Pulsar committers are also BookKeeper committers. So we maintain both projects. For Pulsar we are trying to make sure Pulsar is leveraging critical bug fixes or enhancements from BookKeeper. > > - > - As a product we always support upgrade and rollback for all > components. I understand from Apache Bookkeeper documents that, rollback is > not supported out of box. In that case if we have to rollback Pulsar alone, > can we deploy Apache Bookkeeper separately and configure Pulsar to use the > existing bookkeeper cluster instead of using the bookkeeper provided by > Pulsar. > > Yes you can do that. > > - I guess this will help us to upgrade/rollback Pulsar independent of > Bookkeeper. Please let me know does this sound a good option? > > Yes. that would work. > > - > - If we can deploy our own Apache Bookkeeper & Zookeeper, is there > any supported compatibility matrix documented by Pulsar for Bookkeeper > and > Zookeeper? > > Typically both Pulsar and bookkeepers provide great backward compatibility between versions. A general rule is to make sure the version of bookies is newer or the same as the bookkeeper client used by Pulsar broker. > > - > > > > Regards, > > Subash Kunjupillai > > >
