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

Posted to issues@nifi.apache.org by jomach <gi...@git.apache.org> on 2018/01/02 18:43:40 UTC

[GitHub] nifi issue #2360: NIFI-4323 Wrapped Get/ListHDFS hadoop operations in ugi.do...

Github user jomach commented on the issue:

    https://github.com/apache/nifi/pull/2360
  
    So The Fix is removing the Nifi Thread that renews the Kerberos Token ? 
    From what I noticed until using the UserGroupInformation class is that if I call the method loginUserFromKeytab it will be set for the complete JVM, not allowing scenarios where Nifi needs to connect to two different Hadoop clusters with Kerberos. If we use loginUserFromKeytabAndReturnUGI it will be contained in that returned Object.  I looked at the code verz quickly and it seems that we removed the Thread that takes care of renewing the token.  Could we leverage something like: UserGroupInformation.checkTGTAndReloginFromKeytab or we could trigger  UserGroupInformation.spawnAutoRenewalThreadForUserCreds using UserGroupInformation.loginUserFromSubject


---