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

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

Commit a0ec73097aba236a793159da7f9edc4ecac0b320 in nifi's branch 
refs/heads/support/nifi-1.x from Mark Bathori
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a0ec73097a ]

NIFI-13722: Kerberos ticket renewal issue due static thread pool in Iceberg 
library

This closes #9305.

Signed-off-by: Peter Turcsanyi <[email protected]>


> Kerberos ticket renewal issue due static thread pool in Iceberg library
> -----------------------------------------------------------------------
>
>                 Key: NIFI-13722
>                 URL: https://issues.apache.org/jira/browse/NIFI-13722
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Mark Bathori
>            Assignee: Mark Bathori
>            Priority: Major
>             Fix For: 2.0.0-M5
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> There is a static worker Thread Pool in Iceberg which is used in multiple 
> parts of the library:
> https://github.com/apache/iceberg/blob/main/core/src/main/java/org/apache/iceberg/util/ThreadPools.java#L45
>  
> When the PutIceberg processor is started for the first time then this Thread 
> Pool will be initialized with the initial Kerberos user and the processor 
> will work properly until it is not restarted. When restart happens then a new 
> Kerberos user will be initialized but the Thread Pool will still reference to 
> the original Kerberos user so when the Kerberos ticket expires for the first 
> user then it won't be able to renew it. 
> Same issue happens when multiple processors are using the same classloader 
> and the processor which initialized the Thread Pool is stopped then the other 
> processors will start to fail.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to