You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ramya R (JIRA)" <ji...@apache.org> on 2009/12/18 10:01:19 UTC
[jira] Created: (MAPREDUCE-1315) taskdetails.jsp and
jobfailures.jsp should have consistent convention for machine names in case
of lost task tracker
taskdetails.jsp and jobfailures.jsp should have consistent convention for machine names in case of lost task tracker
--------------------------------------------------------------------------------------------------------------------
Key: MAPREDUCE-1315
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1315
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: jobtracker
Affects Versions: 0.20.1
Reporter: Ramya R
Priority: Minor
Fix For: 0.20.2
Machine names displayed in taskdetails.jsp and jobfailures,jsp show inconsistency in convention in case of lost TT i.e in case of lost TT the machine name is displayed as "tracker_<hostname>:localhost/127.0.0.1:<port>" (not a hyperlink) whereas for other TTs the name displayed is <hostname> (hyperlink). Ideally the machine names should follow a single convention.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1315) taskdetails.jsp and
jobfailures.jsp should have consistent convention for machine names in case
of lost task tracker
Posted by "Ramya R (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramya R updated MAPREDUCE-1315:
-------------------------------
Attachment: TaskDetails.png
Attaching the snapshot of taskdetails.jsp showing the inconsistency.
> taskdetails.jsp and jobfailures.jsp should have consistent convention for machine names in case of lost task tracker
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1315
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1315
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Affects Versions: 0.20.1
> Reporter: Ramya R
> Priority: Minor
> Fix For: 0.20.2
>
> Attachments: TaskDetails.png
>
>
> Machine names displayed in taskdetails.jsp and jobfailures,jsp show inconsistency in convention in case of lost TT i.e in case of lost TT the machine name is displayed as "tracker_<hostname>:localhost/127.0.0.1:<port>" (not a hyperlink) whereas for other TTs the name displayed is <hostname> (hyperlink). Ideally the machine names should follow a single convention.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1315) taskdetails.jsp and
jobfailures.jsp should have consistent convention for machine names in case
of lost task tracker
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated MAPREDUCE-1315:
-------------------------------------
Fix Version/s: (was: 0.20.2)
> taskdetails.jsp and jobfailures.jsp should have consistent convention for machine names in case of lost task tracker
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1315
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1315
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Affects Versions: 0.20.1
> Reporter: Ramya R
> Priority: Minor
> Attachments: TaskDetails.png
>
>
> Machine names displayed in taskdetails.jsp and jobfailures,jsp show inconsistency in convention in case of lost TT i.e in case of lost TT the machine name is displayed as "tracker_<hostname>:localhost/127.0.0.1:<port>" (not a hyperlink) whereas for other TTs the name displayed is <hostname> (hyperlink). Ideally the machine names should follow a single convention.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.