Hi Koji,
I am seeing many issues to get this to run reliably. When running this with
a few flowfiles at a time, and stepping through by switching processors on
and off it works mostly fine, but running this at volume I receive many
errors about "no release signal found"
I have tried to fix this
Hello,
Although I encountered various Kerberos related error, I haven't
encountered that one.
I tried to reproduce the same error by changing Kerberos related
configuration, but to no avail.
I recommend enabling Kerberos debug option for further debugging.
You can add the option at
jim
please only post to one list.
users is good for this.
thanks
joe
On Tue, May 29, 2018, 3:54 PM James McMahon wrote:
> Good evening. I have recently migrated my nifi service host server from
> local resolution of users and groups to use an LDAP server. I configured
>
Good evening. I have recently migrated my nifi service host server from
local resolution of users and groups to use an LDAP server. I configured
login-identity-providers.xml and
nifi.security.user.login.identity.provider. I verified my configuration is
known to NiFi by first restarting my nifi
Hi ,
We are getting below error on randomly for few minutes and then goes away, its
coming in PUThiveql
2018-05-29 01:01:07,279 INFO [Timer-Driven Process Thread-95]
org.apache.hive.jdbc.HiveConnection Will try to open client transport with JDBC
Uri:
Hello,
The short answer is that you currently can't do a true zero downtime
deployment of NARs.
The longer answer...
When a node joins the cluster there is a comparison done between the
node's flow and the node's NARs against the cluster's flow and
cluster's NARs. In the case of the flow, if
