[
https://issues.apache.org/jira/browse/HADOOP-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551670
]
Konstantin Shvachko commented on HADOOP-2385:
---------------------------------------------
I think this should be related to all hadoop components including hdfs client,
secondary-node, job-tracker and task-tracker.
They all should independently verify parameters they depend upon.
I'd prefer if we had a separate configuration class for each component, say
NamenodeConfiguration, DatanodeConfiguration, ...
derived from the base Configuration class, with explicit getters and setters
for each parameter used in the component.
That way it will be easy to provide verification and backward compatibility.
That reminds me about one abandoned issue HADOOP-24 - an attempt to make a
configuration interface.
What was the reason it had never been committed?
We should also use xml schema for the verification purposes. That would make
verification automatic, and there will be no
need to write verification code.
> Validate configuration parameters
> ---------------------------------
>
> Key: HADOOP-2385
> URL: https://issues.apache.org/jira/browse/HADOOP-2385
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Robert Chansler
>
> Configuration parameters should be fully validated before name nodes or data
> nodes begin service.
> Required parameters must be present.
> Required and optional parameters must have values of proper type and range.
> Undefined parameters must not be present.
> (I was recently observing some confusion whose root cause was a mis-spelled
> parameter.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
