[ https://issues.apache.org/jira/browse/HADOOP-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557147#comment-13557147 ]
Zesheng Wu commented on HADOOP-9223: ------------------------------------ Thanks Harsh. It's certain that the Tool and ToolRunner can fix the above senario, but not all programs are suitable to run with Tool or ToolRunner interfaces. For example, in our deploy system, we deploy hadoop programs using our own deploy scripts(start/stop, etc), suppose that if we want to start namenode using our own start.sh, we pass config items by -D options, in this senario, the Tool/ToolRunner interface is not so suitalbe. I wish I expressed myself clearly. > support specify config items through system property > ---------------------------------------------------- > > Key: HADOOP-9223 > URL: https://issues.apache.org/jira/browse/HADOOP-9223 > Project: Hadoop Common > Issue Type: Improvement > Components: conf > Affects Versions: 2.0.0-alpha > Reporter: Zesheng Wu > Priority: Minor > Labels: configuration, hadoop > Fix For: 2.0.0-alpha > > Attachments: HADOOP-9223.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > The current hadoop config items are mainly interpolated from the *-site.xml > files. In our production environment, we need a mechanism that can specify > config items through system properties, which is something like the gflags in > system built with C++, it's really very handy. > The main purpose of this patch is to improve the convenience of hadoop > systems, especially when people do testing or perf tuning, which always need > to modify the *-site.xml files > If this patch is applied, then people can start hadoop programs in this way: > java -cp $class_path -Dhadoop.property.$name=$value $program -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira