You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Tony Kurc (JIRA)" <ji...@apache.org> on 2015/10/25 06:04:27 UTC
[jira] [Resolved] (NIFI-997) Kerberos tickets are not being renewed
by Hadoop
[ https://issues.apache.org/jira/browse/NIFI-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Kurc resolved NIFI-997.
----------------------------
Resolution: Fixed
> Kerberos tickets are not being renewed by Hadoop
> ------------------------------------------------
>
> Key: NIFI-997
> URL: https://issues.apache.org/jira/browse/NIFI-997
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Ricky Saltzer
> Assignee: Ricky Saltzer
>
> I've discovered after some time of having kerberos enabled processors, that the kerberos ticket is not being renewed as it should. This is strange because according to HADOOP-6656, this should be automatically taken care of with a utility thread. I examined the NiFi jstack and saw that the renewal thread was present, so I'm not sure what's going on.
> Does NiFi do something with the processor threads that cause child threads to suspend? I have a patch that I'm currently testing (currently looking good), that will renew the kerberos ticket on getFileSystem() if a threshold is reached (e.g. 4 hours).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)