[
https://issues.apache.org/jira/browse/HADOOP-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573377#action_12573377
]
Nigel Daley commented on HADOOP-2911:
-------------------------------------
Here are some other typo's that could also be fixed as part of this:
> % hod -o "allocate ~/tmp 3"
> INFO - Service Registry Started.
> INFO - Hod Job successfully submitted. JobId :
> 9277.gs203000.inktomisearch.com.
> INFO - Ringmaster at : http://gs203031:36333/.
> INFO - HDFS UI on http://gs203031.inktomisearch.com:57972
> INFO - Mapred UI on http://gs203033.inktomisearch.com:54712
Remove periods from the end of lines
on -> at
----------------------
> % hod -o "allocate ~/tmp 300"
> INFO - Service Registry Started.
lower case "Started"
> CRITICAL - Caught signal 2.
> INFO - Hod Interrupted. Cleaning up and exitting
Interrupted. -> interrupted.
exitting -> exiting.
> INFO - Job 9278.gs203000.inktomisearch.com qdelled.
qdelled. -> deleted from queue.
> CRITICAL - op: allocate ~/tmp 300 failed because of an process interrupt.
an -> a
> [HOD] Make the information printed by allocate and info commands less verbose
> and clearer
> -----------------------------------------------------------------------------------------
>
> Key: HADOOP-2911
> URL: https://issues.apache.org/jira/browse/HADOOP-2911
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/hod
> Affects Versions: 0.16.0
> Reporter: Hemanth Yamijala
> Assignee: Vinod Kumar Vavilapalli
> Fix For: 0.16.1
>
>
> Currently hod prints the following information as part of the allocate
> command at an 'INFO' verbose level:
> Service Registry started
> Torque job id
> Ringmaster ..
> HDFS UI at ..
> Mapred UI at ..
> The "service registry started" line is misleading and isn't very useful. This
> should be removed.
> Torque job id is misleading in terminology because job id also clashes with
> Mapred "job id". The proposal is to make it something like 'cluster id' or
> something similar.
> Ringmaster information is useful for debugging, but not for regular users.
> Similar changes should be made to the hod info command as well. The naming
> should be clear and consistent. There, we print all of the above information
> and in addition, also print the number of nodes as min,max. Because we don't
> really support the min,max number of nodes, we can remove that and probably
> print only the number of nodes allocated.
> All information must continue to be printed at a higher verbosity level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
