nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NIFI-997) Kerberos tickets are not being renewed by Hadoop
Date Fri, 23 Oct 2015 19:58:27 GMT


ASF GitHub Bot commented on NIFI-997:

Github user rickysaltzer commented on the pull request:
    I don't think we would have NPE'd because of the order that getFileSystem() ends up being
called, but it's good to take care of anyway just in case. 

> Kerberos tickets are not being renewed by Hadoop
> ------------------------------------------------
>                 Key: NIFI-997
>                 URL:
>             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

View raw message