[NIFI-4350] Remove relogin period parameter from Hadoop processors

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: Extensions
• Assignee: Unassigned
• Reporter: Pierre Villard
• Created: 05/Sep/17 20:23
• Updated: 03/Jan/18 16:35
• Resolved: 03/Jan/18 16:35

Description

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.

Issue Links

• is related to: NIFI-3472 Kerberos relogin not working (tgt) after ticket expires for HDFS/Hive/HBase processors
• is related to: NIFI-4318 Processor cannot be stopped when Kerberos authentication default to prompt
• links to: https://github.com/apache/nifi/pull/2360