[
https://issues.apache.org/jira/browse/HADOOP-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584922#action_12584922
]
Hadoop QA commented on HADOOP-2551:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12379176/HADOOP-2551.patch
against trunk revision 643282.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler
warnings.
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2128/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2128/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2128/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2128/console
This message is automatically generated.
> hadoop-env.sh needs finer granularity
> -------------------------------------
>
> Key: HADOOP-2551
> URL: https://issues.apache.org/jira/browse/HADOOP-2551
> Project: Hadoop Core
> Issue Type: Improvement
> Components: scripts
> Reporter: Allen Wittenauer
> Assignee: Raghu Angadi
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: HADOOP-2551.patch
>
>
> We often configure our HADOOP_OPTS on the name node to have JMX running so
> that we can do JVM monitoring. But doing so means that we need to edit this
> file if we want to run other hadoop commands, such as fsck. It would be
> useful if hadoop-env.sh was refactored a bit so that there were different
> and/or cascading HADOOP_OPTS dependent upon which process/task was being
> performed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.