[jira] [Commented] (NIFI-4350) Remove relogin period parameter from Hadoop processors

["Koji Kawamura (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303003#comment-16303003 ] 

Koji Kawamura commented on NIFI-4350:
-------------------------------------

The changes for NIFI-4323 removes Re-login period parameter and the Kerberos ticket renewal thread from NiFi. Once NIFI-4323 is resolved, this issue should be addressed, too.
https://github.com/apache/nifi/pull/2360

> Remove relogin period parameter from Hadoop processors
> ------------------------------------------------------
>
>                 Key: NIFI-4350
>                 URL: https://issues.apache.org/jira/browse/NIFI-4350
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Pierre Villard
>
> Right now, in Hadoop processors, there is a re-login period parameter that will define when the Kerberos ticket must be renewed by the processor. This re-login method will not take into account the lifetime of the generated ticket as the Hadoop library does (when requiring a new ticket, one will be actually generated only after 80% of the current ticket lifetime).
> With the current situation, in very specific sets of parameters for relogin period, ticket lifetime and processor scheduling, we can be in a situation where we try to execute the code without actually renewing the ticket. The re-login parameter / code should be removed to rely on the one provided by the underlying Hadoop library. 
> Workaround is to lower the re-login period parameter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)