Thanks, after I fired this email I saw that. We'll try a couple different things. I will assume this will not work and will switch the consumers using a route with partition-offsets.
If there is any other information, please let me know. [image: Payoff, Inc.] *Jeremy Farbota* Software Engineer, Data Payoff, Inc. [email protected] (217) 898-8110 <+2178988110> On Thu, Jun 15, 2017 at 4:16 PM, Neil Derraugh < [email protected]> wrote: > Hi Jeremy, > > Take a gander at https://lists.apache.org/thread.html/ > 16178b7fecc92ddc72502cc99068a4207070d2433d86f52d0967b9c4@% > 3Cusers.nifi.apache.org%3E. > > Neil > > On Thu, Jun 15, 2017 at 3:23 PM, Jeremy Farbota <[email protected]> > wrote: > >> We're preparing to upgrade our cluster from 1.0.0 to 1.3.0. >> >> We're using external zookeeper. >> >> We're wondering if we can simply expand the cluster with 1.3.0 machines >> and then turn off the other ones to keep processes running. Are there >> issues with attempting that? Is there an upgrade guide someone for clusters >> on Wiki? >> >> We have kafka consumers and other maintenance processes that are running >> in production so we'd like to make the change without messing with the >> state of those consumers if possible. >> >> Kindly, >> >> >> [image: Payoff, Inc.] >> *Jeremy Farbota* >> Software Engineer, Data >> Payoff, Inc. >> >> [email protected] >> (217) 898-8110 <+2178988110> >> > >
