[
https://issues.apache.org/jira/browse/NIFI-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971006#comment-14971006
]
ASF GitHub Bot commented on NIFI-997:
-------------------------------------
Github user rickysaltzer commented on the pull request:
https://github.com/apache/nifi/pull/97#issuecomment-150578022
I agree with you on the tuple within a tuple, it is pretty confusing. I'll
work on getting these moved into its own class. You're right, error handling is
a bit tricky in this area of the code in order to avoid breaking API changes. I
did the division by 1000 since the threshold is in seconds, but I could change
that. Precision isn't a big deal here since the renewal isn't millisecond (or
even second) time sensitive.
> 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
> 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)
