Hi Chris, Bryan, Thanks for the answers.
How to configure "follower" Registries to pull from the "leader" automatically? What if one of the Registries goes down, how to recover, is it tricky? We have three separated envs, with separated nifi registries. Is it even required to have git as a persistence layer? What is the difference if we setup just file persistence layer in comparison to git? I know Toolkit CLI can be used in our case for transfering the flows between registries, but I'm curious and want to know pros and cons of having one git repo for all the registries. Thanks, Tom -----Original Message----- From: Bryan Bende <bbe...@gmail.com> Sent: 23 June 2021 14:58 To: users@nifi.apache.org Subject: Re: Nifi Registry git presistence It wasn't really meant for that, but as others pointed out, if only one of the registries is doing writes and the others are read-only for pulling into nifi in another environment, then it can work. The best option is to have one central registry that all nifi's can access (if you are willing to access the same git repo from all environments, then why not the same nifi registry?). The second best option is the database persistence provider, with all registries pointing at the same database. On Wed, Jun 23, 2021 at 7:56 AM Chris McKeever <cgmckee...@gmail.com> wrote: > > Yes -- however: > - only one should be the authority > - see the older thread of how you need to have the read-only-clients re-poll > the remote git in order ot pick up the latest changes. > > On Wed, Jun 23, 2021 at 5:25 AM Tomislav Novosel > <tomislav.novo...@clearpeaks.com> wrote: >> >> Hi to all, >> >> >> >> i sit possible to have one central Git repo for multiple NiFi >> registries >> >> as persistance layer? >> >> Ii it possible to configure, for example, three NiFi registries >> (through providers.xml file) >> >> to communicate with one git repo? >> >> >> >> Thanks, >> >> Tom
