Thanks Manikumar for replying. One more query regarding your first reply What if I set both inter.broker.protocol.version & log.message.format.version to 0.10 and update the binaries? How is Kafka supposed to behave & what we are going to miss?
On Wed, Dec 6, 2017 at 12:34 PM, Manikumar <manikumar.re...@gmail.com> wrote: > Hi, > > 1. inter.broker.protocol.version should be higher than or equal to > log.message.format.version. > So with 0.10 inter.broker.protocol.version, we can not use latest message > format and broker wont start. > > 2. Since other brokers in the cluster don't understand latest protocol, we > can not directly > set inter.broker.protocol.version = 1.0 and restart the broker. In first > restart, we will update the binaries > and in second restart we will change the protocol. > > we should follow the steps given in the docs. > > On Wed, Dec 6, 2017 at 11:21 AM, Debraj Manna <subharaj.ma...@gmail.com> > wrote: > > > Hi > > > > Anyone any thoughts? > > > > > > > > On Tue, Dec 5, 2017 at 8:38 PM, Debraj Manna <subharaj.ma...@gmail.com> > > wrote: > > > > > Hi > > > > > > Regarding the Kafka Rolling Upgrade steps as mentioned in the doc > > > <https://kafka.apache.org/documentation/#upgrade> > > > > > > Can you let me know how is Kafka supposed to behave if the binaries are > > > upgraded to the latest 1.0 but inter.broker.protocol.version still > points > > > to 0.10 in all the brokers? What features will I be missing in Kafka > 1.0 > > > and what problem I am expected to behave? > > > > > > Also can you let me know in rolling upgrade (from 0.10 to 1.0) if I > > follow > > > the below steps how are Kafka supposed to behave > > > > > > > > > 1. Add inter.broker.protocol.version = 1.0 in a broker update the > > > binary and restart it. > > > 2. Then go to the other brokers one by one and repeat the above > steps > > > > > > > > >
