You are correct, the moment a RPG is added to the canvas a background thread will attempt to fetch the Site-to-Site details from the configure remote NiFi. There is no way to disable this. RPGs only give you the ability to enable or disable transmission of FlowFiles to/from remote ports.
On Wed, May 4, 2022, 6:11 AM Isha Lamboo <[email protected]> wrote: > Hi Juan, > > > > Thank you for the reply. I assume you mean the > nifi.flowcontroller.autoResumeState=false setting. I’m already using that > to ensure no flows started before we want them to. My problem is that the > RPGs keep trying to retrieve the site-to-site details regardless. > > > > Isha > > > > *Van:* Juan Pablo Gardella <[email protected]> > *Verzonden:* woensdag 4 mei 2022 11:36 > *Aan:* [email protected] > *Onderwerp:* Re: Is it possible to completely disable RPGs, not just > transmission? > > > > 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 > > > >
