You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2006/04/18 17:50:17 UTC
[jira] Created: (HADOOP-144) the dfs client id isn't relatable to
the map/reduce task ids
the dfs client id isn't relatable to the map/reduce task ids
------------------------------------------------------------
Key: HADOOP-144
URL: http://issues.apache.org/jira/browse/HADOOP-144
Project: Hadoop
Type: Improvement
Components: dfs
Versions: 0.1.1
Reporter: Owen O'Malley
Assigned to: Owen O'Malley
Fix For: 0.2
>From the dfs logs you can't tell which map/reduce tasks where involved, which makes debugging harder.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (HADOOP-144) the dfs client id isn't relatable to
the map/reduce task ids
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-144?page=all ]
Doug Cutting resolved HADOOP-144:
---------------------------------
Resolution: Fixed
I just committed this. Thanks, Owen!
> the dfs client id isn't relatable to the map/reduce task ids
> ------------------------------------------------------------
>
> Key: HADOOP-144
> URL: http://issues.apache.org/jira/browse/HADOOP-144
> Project: Hadoop
> Type: Improvement
> Components: dfs
> Versions: 0.1.1
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.2
> Attachments: dfs-client-name.patch
>
> From the dfs logs you can't tell which map/reduce tasks where involved, which makes debugging harder.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-144) the dfs client id isn't relatable to
the map/reduce task ids
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-144?page=all ]
Owen O'Malley updated HADOOP-144:
---------------------------------
Attachment: dfs-client-name.patch
This patch sets the task id in the task's local job conf and the dfs client will use the "mapred.task.id" from the Configuration, if it is defined.
> the dfs client id isn't relatable to the map/reduce task ids
> ------------------------------------------------------------
>
> Key: HADOOP-144
> URL: http://issues.apache.org/jira/browse/HADOOP-144
> Project: Hadoop
> Type: Improvement
> Components: dfs
> Versions: 0.1.1
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.2
> Attachments: dfs-client-name.patch
>
> From the dfs logs you can't tell which map/reduce tasks where involved, which makes debugging harder.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-144) the dfs client id isn't relatable to
the map/reduce task ids
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-144?page=comments#action_12374960 ]
Owen O'Malley commented on HADOOP-144:
--------------------------------------
So instead of DFS client names like: DFSClient_2114239722
For map/reduce tasks, I get client names like: DFSClient_task_r_dgi5u
They are still random strings, but at least they are tied to the map/reduce logs.
> the dfs client id isn't relatable to the map/reduce task ids
> ------------------------------------------------------------
>
> Key: HADOOP-144
> URL: http://issues.apache.org/jira/browse/HADOOP-144
> Project: Hadoop
> Type: Improvement
> Components: dfs
> Versions: 0.1.1
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.2
> Attachments: dfs-client-name.patch
>
> From the dfs logs you can't tell which map/reduce tasks where involved, which makes debugging harder.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira