[
https://issues.apache.org/jira/browse/HADOOP-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616066#action_12616066
]
Hemanth Yamijala commented on HADOOP-3808:
------------------------------------------
Hudson is not picking up new patches. I ran test-patch locally, and got the
following results:
[exec] -1 overall.
[exec] +1 @author. The patch does not contain any @author tags.
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
There are no test cases in the patch because the feature is dependent on the
Torque resource manager functionality, and it will require some effort to
develop mock stubs for this feature.
I also ran ant test on my machine, and TEST-org.apache.hadoop.cli.TestCLI.txt
failed. However, it is unrelated to the patch, as HOD does not affect any part
of Hadoop.
Can this patch be committed to trunk and the 0.18 branch based on above ?
> [HOD] Include job tracker RPC in notes attribute after job submission
> ---------------------------------------------------------------------
>
> Key: HADOOP-3808
> URL: https://issues.apache.org/jira/browse/HADOOP-3808
> Project: Hadoop Core
> Issue Type: Improvement
> Affects Versions: 0.18.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: HADOOP-3808.1.patch, HADOOP-3808.patch
>
>
> Currently, after a job is submitted, HOD records the Jobtracker URL and the
> NameNode URL in the 'notes' attribute of the Torque resource manager. This
> helps in building centralized administration tools that need to get a full
> picture of all allocated clusters etc. Including the Jobtracker RPC port in
> this attribute would be useful to build such similar tools. One of them is an
> idle job tracker that can be centrally run to clear up any clusters that
> aren't automatically cleaned up due to some faulty nodes in the cluster or
> resource manager problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
