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 "Bejoy KS (Created) (JIRA)" <ji...@apache.org> on 2012/01/16 18:35:41 UTC
[jira] [Created] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
The Map tasks logs should have the value of input split it processed
--------------------------------------------------------------------
Key: MAPREDUCE-3678
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
Project: Hadoop Map/Reduce
Issue Type: New Feature
Components: nodemanager, tasktracker
Affects Versions: 1.0.0, 0.20.205.0, 0.20.203.0
Environment: Linux red hat.
Reporter: Bejoy KS
It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
Sample as
Input Split
hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated MAPREDUCE-3678:
-------------------------------
Release Note: A map-task's syslogs now carries basic info on the InputSplit it processed. (was: A Map Task's syslogs now carries basic info on the InputSplit it processed.)
Status: Patch Available (was: Open)
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 2.0.0-alpha, 1.0.0
> Reporter: Bejoy KS
> Assignee: Harsh J
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Arun C Murthy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187427#comment-13187427 ]
Arun C Murthy commented on MAPREDUCE-3678:
------------------------------------------
AFAIK MR1 already shows this in taskdetails.jsp - we need to add this to MR2.
Also, AFAIK, I thought MR1 task-logs had this info logged, something I see missing in MR2 also.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 0.20.203.0, 0.20.205.0, 1.0.0
> Environment: Linux red hat.
> Reporter: Bejoy KS
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated MAPREDUCE-3678:
-------------------------------
Environment: (was: Linux red hat.)
Target Version/s: 1.2.0, 2.2.0-alpha
Affects Version/s: (was: 0.20.205.0)
(was: 0.20.203.0)
2.0.0-alpha
Release Note: A Map Task's syslogs now carries basic info on the InputSplit it processed.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated MAPREDUCE-3678:
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0.3-alpha
1.2.0
Target Version/s: (was: 1.2.0, 2.0.2-alpha)
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks Tom. I committed this to trunk, branch-2 and branch-1.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471221#comment-13471221 ]
Harsh J commented on MAPREDUCE-3678:
------------------------------------
Hi,
If no one has any objections to these INFO log additions, I'll commit it in in a couple of days.
This helps projects such as Pig, Hive, etc. without any changes on their end.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187044#comment-13187044 ]
Harsh J commented on MAPREDUCE-3678:
------------------------------------
Task's own logs are the best place for this, not the daemons.
The reason it is tedious to do/maintain at the framework level is that not all InputSplits may be FileSplits, and formats that do use FileSplits may use them in different ways as well (CombineFileIF, for instance).
The InputSplit interface by itself is path-agnostic.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 0.20.203.0, 0.20.205.0, 1.0.0
> Environment: Linux red hat.
> Reporter: Bejoy KS
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J reassigned MAPREDUCE-3678:
----------------------------------
Assignee: Harsh J
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 0.20.203.0, 0.20.205.0, 1.0.0
> Environment: Linux red hat.
> Reporter: Bejoy KS
> Assignee: Harsh J
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated MAPREDUCE-3678:
-------------------------------
Attachment: MAPREDUCE-3678-branch-1.patch
Patch for branch-1.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Attachments: MAPREDUCE-3678-branch-1.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated MAPREDUCE-3678:
-------------------------------
Component/s: (was: nodemanager)
(was: tasktracker)
mrv2
mrv1
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421594#comment-13421594 ]
Harsh J commented on MAPREDUCE-3678:
------------------------------------
bq. Once the job is in history viewer currently do we have any option to find this information?
Unsure about this one, we can probably handle via another JIRA if its important to know via JH too (minus userlogs, i.e.). I'll file a new one after completing up the patches.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 0.20.203.0, 0.20.205.0, 1.0.0
> Environment: Linux red hat.
> Reporter: Bejoy KS
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472427#comment-13472427 ]
Hudson commented on MAPREDUCE-3678:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #2858 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2858/])
MAPREDUCE-3678. The Map tasks logs should have the value of input split it processed. Contributed by Harsh J. (harsh) (Revision 1396032)
Result = FAILURE
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396032
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Bejoy KS (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187487#comment-13187487 ]
Bejoy KS commented on MAPREDUCE-3678:
-------------------------------------
Ya it is available in taskdetails.jsp . But when we have a large number of jobs running on our cluster in a matter of half an hour the jobs would be in history and in in jobtaskshistory.jsp there are only the following values
-Task Id
-Start Time
-Finish Time
-Error
Can we have one more filed here similar to status in taskdetails.jsp that would show the input split it processed as well.
Once the job is in history viewer currently do we have any option to find this information?
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 0.20.203.0, 0.20.205.0, 1.0.0
> Environment: Linux red hat.
> Reporter: Bejoy KS
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421593#comment-13421593 ]
Harsh J commented on MAPREDUCE-3678:
------------------------------------
Hi Arun,
bq. AFAIK MR1 already shows this in taskdetails.jsp - we need to add this to MR2.
But this state is wiped away if the task sets a status. So I don't find it reliable :(
bq. Also, AFAIK, I thought MR1 task-logs had this info logged, something I see missing in MR2 also.
We do not log this at all. I'll post patches that target both.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 0.20.203.0, 0.20.205.0, 1.0.0
> Environment: Linux red hat.
> Reporter: Bejoy KS
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472275#comment-13472275 ]
Tom White commented on MAPREDUCE-3678:
--------------------------------------
+1
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472372#comment-13472372 ]
Hudson commented on MAPREDUCE-3678:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2897 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2897/])
MAPREDUCE-3678. The Map tasks logs should have the value of input split it processed. Contributed by Harsh J. (harsh) (Revision 1396032)
Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396032
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473237#comment-13473237 ]
Hudson commented on MAPREDUCE-3678:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #1222 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1222/])
MAPREDUCE-3678. The Map tasks logs should have the value of input split it processed. Contributed by Harsh J. (harsh) (Revision 1396032)
Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396032
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472375#comment-13472375 ]
Hudson commented on MAPREDUCE-3678:
-----------------------------------
Integrated in Hadoop-Common-trunk-Commit #2835 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2835/])
MAPREDUCE-3678. The Map tasks logs should have the value of input split it processed. Contributed by Harsh J. (harsh) (Revision 1396032)
Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396032
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473198#comment-13473198 ]
Hudson commented on MAPREDUCE-3678:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk #1191 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1191/])
MAPREDUCE-3678. The Map tasks logs should have the value of input split it processed. Contributed by Harsh J. (harsh) (Revision 1396032)
Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396032
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421635#comment-13421635 ]
Hadoop QA commented on MAPREDUCE-3678:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12537726/MAPREDUCE-3678.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2653//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2653//console
This message is automatically generated.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3678) The Map tasks logs should have
the value of input split it processed
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated MAPREDUCE-3678:
-------------------------------
Attachment: MAPREDUCE-3678.patch
Patch for trunk attached.
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: nodemanager, tasktracker
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the input split processed by that task. Map reduce task tracker log should accommodate the same. Also in the jobdetails web UI, the split also should be displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large data volume processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira