You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/03 13:12:00 UTC

[jira] [Commented] (NIFI-5134) NiFi can encounter "no TGT" after Hive service outage

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

ASF GitHub Bot commented on NIFI-5134:
--------------------------------------

Github user mattyb149 commented on the issue:

    https://github.com/apache/nifi/pull/2667
  
    +1 LGTM, looks like it will work like a barrier sync, the first one in will relogin if necessary, the rest will no-op, which means there won't be a race condition / threading issue when some of the threads call doAs. Thanks for the improvement! Merging to master


> NiFi can encounter "no TGT" after Hive service outage
> -----------------------------------------------------
>
>                 Key: NIFI-5134
>                 URL: https://issues.apache.org/jira/browse/NIFI-5134
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.6.0
>            Reporter: Jeff Storck
>            Assignee: Jeff Storck
>            Priority: Major
>
> NiFi's Hive controller service may encounter a "no TGT" error after an outage in Hive has occurred.  The "no TGT" error can occur after the service has been restarted and the current TGT has expired.  The Hive client/thrift does not seem to handle this case implicitly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)