You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "wangzhixiang (Jira)" <ji...@apache.org> on 2020/01/13 08:17:00 UTC
[jira] [Updated] (HDFS-15115) Namenode crash caused by NPE in
BlockPlacementPolicyDefault when dynamically change logger to debug
[ https://issues.apache.org/jira/browse/HDFS-15115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
wangzhixiang updated HDFS-15115:
--------------------------------
Attachment: (was: 0001-fix-up-the-Namenode-crash-bug-caused-by-dynamically-.patch)
> 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
>
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org