You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2012/10/15 12:00:03 UTC
[jira] [Resolved] (HADOOP-8049) Add entry point/script to do
preflight checking of script resolution
[ https://issues.apache.org/jira/browse/HADOOP-8049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-8049.
------------------------------------
Resolution: Duplicate
> Add entry point/script to do preflight checking of script resolution
> --------------------------------------------------------------------
>
> Key: HADOOP-8049
> URL: https://issues.apache.org/jira/browse/HADOOP-8049
> Project: Hadoop Common
> Issue Type: New Feature
> Components: util
> Affects Versions: 1.0.0, 0.24.0
> Reporter: Steve Loughran
> Priority: Minor
>
> The script supplied by the ops team could have many problems
> # not run
> # have the wrong permissions
> # fail to parse/resolve some or all hosts
> # not be the string set in the configuration file.
> Diagnostics could be improved here with an entry point that
> # reads in the configuration file
> # instantiates whatever mapper is declared
> # attempts to resolve all hosts passed in as arguments, logging success and failures
> # prints out a topology map at the end
> A key goal would be to recognise and report a complete failure to report a mapping as per MAPREDUCE-50, so let people identify problems in their script before updating the cluster
> Test plan
> -Java entry point: invoke it with arguments, get the output as a string and scan.
> -Shell script. Include whatever post-install script tests are being written.
--
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