There is a property on nifi.properties that you can start nifi and all processors are in stop state. I could not find it, but maybe it is useful for that scenario.
On Wed, May 4, 2022 at 5:14 AM Isha Lamboo <[email protected]> wrote: > Hi all, > > > > Is there a way to stop disabled Remote Process Groups from continually > contacting the remote to update the contents? > > > > I’m migrating a cluster with hundreds of Remote Process Groups and the > moment I start up the new cluster with all flows stopped/disabled, the RPGs > all start contacting the remote, regardless of the RPG’s status. > > This results in various errors since firewall ports and remote nifi > policies are not yet in place. I’m worried about the http threads on the > remote NiFi cluster being overloaded and locally, all other errors are > drowned out by the RPG errors. > > > > This seems like a limitation in the Remote Process Group. I can’t even see > the enabled/disabled status while the RPG is failing to update from the > remote instance. > > > > Regards, > > > > Isha > > >
