Hi Dima, In that case, I would recommend just deploying the pre-built docker image in your dev environment instead of running multiple instances together.
I would also suggest as alternative one of 2 things, people experiment locally on their own instances as Nifi is distributed as an archive it can just be run locally or have one instance on a server and ask people to only work in a processes group and not off the root canvas. Edward On Fri, 10 Sep 2021, 17:22 Dmitry Stepanov, <[email protected]> wrote: > Hi Edward, > > You're right - we will be using containers for production. I'm just > testing things out on a sandbox or dev env we already have. > > Thank you, > > On Fri, Sep 10, 2021 at 12:04 PM Edward Armes <[email protected]> > wrote: > >> Hi Dima, >> >> Ideally you should not run anything as the root user as it tends to cause >> more issues then it solves in the long term. >> >> Secondly I would recommend against running more than one Nifi instance >> concurrently on a host without some sort of isolation like a container or a >> jail. >> >> If you're looking to create a multi tenancy Nifi environment then that >> is something that this list should be able to provide guidance on, without >> having to run multiple Nifi instances per host. >> >> Edward >> >> On Fri, 10 Sep 2021, 14:47 Dmitry Stepanov, <[email protected]> wrote: >> >>> Hi Community, >>> Question on the env variables - I plan on using multiple service >>> instances of NiFi running on same server under same user (root). I'm >>> mostly concerned about env variables from "nifi-1.14.0/bin/nifi-env.sh" >>> >>> Thank you for your help, >>> >>> Dima Stepanov >>> >>
