You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Aaron Gresch (Jira)" <ji...@apache.org> on 2020/06/24 14:24:00 UTC
[jira] [Created] (STORM-3656) Change handling of Hadoop TGT renewal
exception
Aaron Gresch created STORM-3656:
-----------------------------------
Summary: 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
Reporter: Aaron Gresch
Assignee: Aaron Gresch
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)