You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2018/01/03 16:36:00 UTC
[jira] [Resolved] (NIFI-4350) Remove relogin period parameter from
Hadoop processors
[ https://issues.apache.org/jira/browse/NIFI-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Witt resolved NIFI-4350.
-------------------------------
Resolution: Fixed
+1 merged to master. Great job!
Approach to document their usage/impact being nullified rather than removed is a best of both worlds approach.
> 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
> Fix For: 1.5.0
>
>
> 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)