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

ASF subversion and git services commented on NIFI-7453:
-------------------------------------------------------

Commit ca65bba5d720550aab97fcfc58be46e1b77001d3 in nifi's branch 
refs/heads/MINIFI-422 from Tamas Palfy
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ca65bba ]

NIFI-7453 In PutKudu creating a new Kudu client when refreshing TGT

NIFI-7453 Creating a new Kudu client when refreshing TGT in 
KerberosPasswordUser as well. (Applied to KerberosKeytabUser only before.)
NIFI-7453 Safely closing old Kudu client before creating a new one.
NIFI-7453 Visibility adjustment.

This closes #4276.

Signed-off-by: Peter Turcsanyi <turcsa...@apache.org>


> PutKudu kerberos issue after TGT expires 
> -----------------------------------------
>
>                 Key: NIFI-7453
>                 URL: https://issues.apache.org/jira/browse/NIFI-7453
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Tamas Palfy
>            Assignee: Tamas Palfy
>            Priority: Major
>             Fix For: 1.12.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When PutKudu is used with kerberos authentication, it stops working when the 
> TGT expires with the following logs/exceptions:
> {noformat}
> ERROR org.apache.nifi.processors.kudu.PutKudu: 
> PutKudu[id=4ad63284-cb39-1c78-bd0e-c280df797039] Failed to write due to Row 
> error for primary key="feebfe81-4ee6-4a8b-91ca-311e1c4f8749", tablet=null, 
> server=null, status=Runtime error: cannot re-acquire authentication token 
> after 5 attempts (Couldn't find a valid master in (HOST:PORT). Exceptions 
> received: [org.apache.kudu.client.NonRecoverableException: server requires 
> authentication, but client does not have Kerberos credentials (tgt). 
> Authentication tokens were not used because this connection will be used to 
> acquire a new token and therefore requires primary credentials])
> 2020-05-13 09:27:05,157 INFO org.apache.kudu.client.ConnectToCluster: Unable 
> to connect to master HOST:PORT: server requires authentication, but client 
> does not have Kerberos credentials (tgt). Authentication tokens were not used 
> because this connection will be used to acquire a new token and therefore 
> requires primary credentials
> 2020-05-13 09:27:05,159 WARN org.apache.kudu.client.AsyncKuduSession: 
> unexpected tablet lookup failure for operation KuduRpc(method=Write, 
> tablet=null, attempt=0, DeadlineTracker(timeout=0, elapsed=15), No traces)
> org.apache.kudu.client.NonRecoverableException: cannot re-acquire 
> authentication token after 5 attempts (Couldn't find a valid master in 
> (HOST:PORT). Exceptions received: [org.apache.kudu.client.NonRecover
> ableException: server requires authentication, but client does not have 
> Kerberos credentials (tgt). Authentication tokens were not used because this 
> connection will be used to acquire a new token and therefore requires primary 
> credentials])
>         at 
> org.apache.kudu.client.AuthnTokenReacquirer$1NewAuthnTokenErrB.call(AuthnTokenReacquirer.java:158)
>         at 
> org.apache.kudu.client.AuthnTokenReacquirer$1NewAuthnTokenErrB.call(AuthnTokenReacquirer.java:141)
>         at com.stumbleupon.async.Deferred.doCall(Deferred.java:1280)
>         at com.stumbleupon.async.Deferred.runCallbacks(Deferred.java:1259)
>         at com.stumbleupon.async.Deferred.callback(Deferred.java:1002)
>         at 
> org.apache.kudu.client.ConnectToCluster.incrementCountAndCheckExhausted(ConnectToCluster.java:246)
> ...
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to