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 "Hudson (JIRA)" <ji...@apache.org> on 2010/02/02 07:18:21 UTC
[jira] Commented: (MAPREDUCE-1314) Some logs have wrong
configuration names.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828487#action_12828487 ]
Hudson commented on MAPREDUCE-1314:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #225 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/225/])
> Some logs have wrong configuration names.
> -----------------------------------------
>
> Key: MAPREDUCE-1314
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: patch-1314.txt
>
>
> After MAPREDUCE-849, some of the logs have wrong configuration names.
> For example :
> 09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.