[ 
https://issues.apache.org/jira/browse/HADOOP-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617805#comment-13617805
 ] 

Steve Loughran commented on HADOOP-9044:
----------------------------------------

I see. The {{resource}} option just does a {{Classloader.loadResource()}} call 
to get a URL, though it would find things like {{/hdfs-site.xml}} and show 
where that came from. e.g. show that that resource came from 
{{file:///etc/hadoop/conf/hdfs-site.xml}}

# we could add a {{--print}} option to print any found resource to the console, 
which could show which log4j and site properties were being loaded.

For real cluster config diagnostics, I'd recommend a separate entry point, 
which could do things like
# list all default XML files
# dump the default configuration
# print specific string values
# assert that a configuration parameter equalled a specified string value. That 
could be good for some sanity checking post-installation too.

I'd make that a separate JIRA though; this one should be ready to go as is, 
with just some documentation
                
> add FindClass main class to provide classpath checking of installations
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-9044
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9044
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: util
>    Affects Versions: 1.1.0, 2.0.3-alpha
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-9044.patch, HADOOP-9044.patch
>
>
> It's useful in postflight checking of a hadoop installation to verify that 
> classes load, especially codes with external JARs and native codecs. 
> An entry point designed to load a named class and create an instance of that 
> class can do this -and be invoked from any shell script or tool that does the 
> installation.

--
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

Reply via email to