[
https://issues.apache.org/jira/browse/HDFS-15115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014562#comment-17014562
]
Wei-Chiu Chuang edited comment on HDFS-15115 at 1/13/20 6:37 PM:
-----------------------------------------------------------------
[~hexiaoqiao] we should add that back. The removal would have been valid if log
object cannot be changed dynamically, which is not the case.
Better to add a UT to prevent this issue from happening again, if that's
possible.
was (Author: jojochuang):
[~hexiaoqiao] we should add that back. The removal would have been valid if log
object cannot be changed dynamically, which is not the case.
> Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamically
> change logger to debug
> ---------------------------------------------------------------------------------------------------
>
> Key: HDFS-15115
> URL: https://issues.apache.org/jira/browse/HDFS-15115
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: wangzhixiang
> Priority: Major
> Attachments: HDFS-15115.001.patch
>
>
> To get debug info, we dynamically change the logger of
> BlockPlacementPolicyDefault to debug when namenode is running. However, the
> Namenode crashs. From the log, we find some NPE in
> BlockPlacementPolicyDefault.chooseRandom. Because *StringBuilder builder*
> will be used 4 times in BlockPlacementPolicyDefault.chooseRandom method.
> While the *builder* only initializes in the first time of this method. If we
> change the logger of BlockPlacementPolicyDefault to debug after the part, the
> *builder* in remaining part is *NULL* and cause *NPE*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
