Hi, Guozhang Is there a way to monitor/check if a broker has catched up most of the replicas of topics in sync?
We are considering an upgrade to 0.8.2.1. A rolling upgrade plan seems possible because we don't wan't to lose any data. It occured to me that rolling upgrade wihout control can still lose data. suppose broker A and broker B both has partition 1. step 1. broker A did an upgrade. partition 1's leader became broker B, data will come into broker B. step 2. broker B did an upgrade too. If broker A has not catched all the recent data from broker B, after broker A has become leader of partition 1, the recent data will lose. the only way seems to wait enough time between step 2 and step 1. but we don't know how much is enough. any better solutions for rolling upgrade? Thanks On Fri, Oct 17, 2014 at 11:12 PM, Guozhang Wang <wangg...@gmail.com> wrote: > Hi Balaji, > > You could do a rolling bounce of the brokers to do the in-place upgrade if > your partitions have at least two replicas. After that you may probably > need to rebalance the leaders if they are not balanced any more. > > Guozhang > > On Wed, Oct 15, 2014 at 10:53 AM, Seshadri, Balaji < > balaji.sesha...@dish.com > > wrote: > > > Hi Guys, > > > > Can you guys share any experiences you had with Live Upgrade ?. > > > > How reliable is it ?.Did we lose messages ?. > > > > What issues did you guys face when doing live upgrade. > > > > We are planning to upgrade to 0.8.2 from 0.8-beta before we move our web > > methods broker based messaging layer to Kafka. > > > > We would like to get your inputs. > > > > Thanks, > > > > Balaji > > > > > > -- > -- Guozhang > -- *Best Regards向河林*
