[ 
https://issues.apache.org/jira/browse/STORM-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron Gresch resolved STORM-3656.
---------------------------------
    Fix Version/s: 2.3.0
       Resolution: Fixed

> Change handling of Hadoop TGT renewal exception
> -----------------------------------------------
>
>                 Key: STORM-3656
>                 URL: https://issues.apache.org/jira/browse/STORM-3656
>             Project: Apache Storm
>          Issue Type: Improvement
>    Affects Versions: 2.2.0
>            Reporter: Aaron Gresch
>            Assignee: Aaron Gresch
>            Priority: Major
>             Fix For: 2.3.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> STORM-3606 identified an issue where Hadoop's TGT auto renewal thread causes 
> an exception and worker restart.  The fix involved a lot of reflection calls 
> to emulate the Hadoop code while avoiding launching this thread.
>  
> It's possible Hadoop could change their code, causing this reflection to 
> fail.   To handle this case, we could instead allow Hadoop to launch this 
> autorenewal thread, and have the worker catch the specific NPE from Hadoop in 
> the exception handler.  



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

Reply via email to