[
https://issues.apache.org/jira/browse/HDFS-17945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101964#comment-18101964
]
ASF GitHub Bot commented on HDFS-17945:
---------------------------------------
johntomcat7408-cmyk commented on PR #8648:
URL: https://github.com/apache/hadoop/pull/8648#issuecomment-5188450882
retest this please
> Invalid checkpoint directory configuration can cause NullPointerException
> during HDFS FileSystem initialization
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-17945
> URL: https://issues.apache.org/jira/browse/HDFS-17945
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client, namenode
> Affects Versions: 3.4.3
> Reporter: jiang he
> Priority: Major
> Labels: pull-request-available
>
> With an invalid checkpoint directory / user home configuration, HDFS client
> initialization fails with a bare NullPointerException.
> The error message does not identify the invalid configuration key or value.
> Reproduction config
> <configuration>
> <property>
> <name>dfs.replication</name>
> <value>1</value>
> </property>
> <property>
> <name>dfs.datanode.data.read.bandwidthPerSec</name>
> <value>0</value>
> </property>
> <property>
> <name>dfs.namenode.block.deletion.lock.threshold.ms</name>
> <value>-1</value>
> </property>
> <property>
> <name>dfs.user.home.dir.prefix</name>
> <value>@name@</value>
> </property>
> <property>
> <name>dfs.namenode.checkpoint.edits.dir</name>
> <value>valid/dir</value>
> </property>
> <property>
> <name>dfs.namenode.block.deletion.unlock.interval.ms</name>
> <value>99999999</value>
> </property>
> <property>
> <name>dfs.namenode.checkpoint.dir</name>
> <value>file://${hadoop.tmp.dir}/dfs/namesecondary</value>
> </property>
> <property>
> <name>dfs.namenode.checkpoint.dir</name>
> <value>@name@</value>
> </property>
> </configuration>
> Observed
> Failed to initialize filesystem hdfs://127.0.0.1:9000:
> java.lang.NullPointerException
> Expected
> HDFS should reject the invalid configuration with a clear error message
> that identifies the invalid key/value, instead of exposing a bare
> NullPointerException.
> Control test
> Using normal path values passes successfully:
> dfs.user.home.dir.prefix=/user
> dfs.namenode.checkpoint.edits.dir=${dfs.namenode.checkpoint.dir}
> dfs.namenode.checkpoint.dir=file://${hadoop.tmp.dir}/dfs/namesecondary
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]