hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2911) [HOD] Make the information printed by allocate and info commands less verbose and clearer
Date Thu, 06 Mar 2008 12:28:58 GMT

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

Hudson commented on HADOOP-2911:

Integrated in Hadoop-trunk #421 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/421/])

> [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
>         Attachments: hadoop-2911, hadoop-2911.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.

View raw message