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
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
wrote:
> Hi Dima,
>
> Ideally you should not run anything as the root user as it tends to cause
>
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 look
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
Hi,
I've been trying to import certain environment variables into Nifi. I know it
is possible to add exports of variables to the nifi-env.sh file. However these
variables are only loaded on a nifi service restart and not added during a
system reboot or systemctl restart.
The reason I l
Using a cluster with three nodes on CentOs 7 and NiFi 1.3.0.
NiFi is unable to access environment variables.
Do we need to list all of our environment variables that NiFi will use in
./bin/nifi-env.sh?
We've been restarting nifi nodes after each new environment variable is
created/set
