If you are asking if this is the correct way to migrate the data from an old ZK to a new one, then yes.
As far as the flow being stopped... if you don't stop it, then flow might continue to modify the state in ZK while you are migrating it, so maybe there is some value of 1 and that gets migrated to the new ZK, but then the old flow runs and updates the value to 2 in your old ZK, now when the flow runs in your new cluster it will start from 1 even though the old cluster already processed 2. On Fri, Mar 27, 2020 at 9:57 AM sanjeet rath <[email protected]> wrote: > Hi, > > If someone could help me with my trailed query, then it would be > really helpful. > I eagerly await for your response. > > Regards, > Sanjeet > > On Thu, Mar 26, 2020 at 3:20 PM sanjeet rath <[email protected]> > wrote: > >> >> Hi Team, >> >> I am trying to achieve Nifi migration to a different cluster using >> zookeeper state migration (in case of failure of cluster) >> >> Steps i am doing. >> >> zk-migrator.sh -r -z >> sourceHostname:sourceClientPort/sourceRootPath/components -f >> /path/to/export/zk-source-data.json >> >> zk-migrator.sh -s -z >> destinationHostname:destinationClientPort/destinationRootPath/components -f >> /path/to/export/zk-source-data.json >> also moved the flow.xml.gz, users.xml, authorization.xml from source >> cluster to the destination cluster. >> >> Then its working fine, means its capturing the processor state id from >> the old cluster. >> >> But my question is: >> >> Is the above approach is correct for moving to new cluster with state >> when there is failure in old cluster. >> And one more thing, as per zk migration doc the flow need be stoped >> before running the zk migration export script. >> Is it mandatory ? >> >> Is there any other approach is there to achieve this, then please suggest, >> >> Thanks, >> Sanjeet >> >> >> >> >> >> >> >> >> >> >> -- >> Sanjeet Kumar Rath, >> mob- +91 8777577470 >> >> > > -- > Sanjeet Kumar Rath, > mob- +91 8777577470 > >
