Isha, When we migrated off of 1.9.1 we faced the same issue. You need to upgrade zookeeper to 3.5.x, better yet you should upgrade to 3.6+ as it allows the zookeeper nodes to be started in any order, otherwise they need to be started in the order of their id.
Vijay > On Jul 8, 2021, at 2:56 PM, Isha Lamboo <[email protected]> > wrote: > > Hi all, > > I’m planning an upgrade of our NiFi 1.9.0 clusters with external Zookeeper > 3.4.6 clusters to NiFi 1.12 or 1.13. > > After rolling out an upgrade of only the NiFi software in our test setup, I > found that NiFi 1.13.2 would not communicate correctly with the unchanged > Zookeeper cluster. > Now I’m wondering if it is misconfiguration (ex. The zookeeper connection > string with the ports separate or combined as in 1.10+) or just > incompatibility. > > So my question to those who have done this before: Should I upgrade Zookeeper > first (to 3.5.x), NiFi first (and fix config errors) or does it need to be > both of them at once? > > As a side note, I haven’t found a compatibility matrix of NiFi and Zookeeper > versions, is this documented somewhere or do I just go with the embedded > Zookeeper version number of the NiFi release? > > Regards, > > Isha Lamboo
smime.p7s
Description: S/MIME cryptographic signature
