Sumo,
I do believe that you should be okay leaving that java.arg.15 in, in that case.
The ZooKeeper Client
will use the "Client" section of that file, if it is defined. In the example
that you provided, that Client section
does not exist, so it is okay. What would not work in this case would be
Thanks Mark.
I had java.arg.15 setting in bootstrap.conf from NiFi 0.4.x to make putHDFS
processor work with my MapR cluster. If I remove it, putHDFS will fail.
Now with NiFi 0.5.1,
if I set nifi.state.management.embedded.zookeeper.start=false ,
can I point to dedicated external ZooKeeper in
Sumo,
If your intent is to use an external ZooKeeper, you should not be starting the
embedded ZooKeeper.
You will also not want to set the java.arg.15 parameter there to point to a
login config file, as that is
necessary only when enabling Kerberos - not for use when security disabled.
So you w
I am getting following error when NiFi Cluster started with embedded
ZooKeeper enabled.
I would like to configure external ZooKeeper for NiFi State Management without
interfering with java.security.auth.login.config setting for MapR HDFS. Can
somebody provide me instructions how to configur
