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 "Michael Bieniosek (JIRA)" <ji...@apache.org> on 2007/07/12 19:19:04 UTC
[jira] Created: (HADOOP-1602) TaskLog.java buffers entire task
userlog in memory
TaskLog.java buffers entire task userlog in memory
--------------------------------------------------
Key: HADOOP-1602
URL: https://issues.apache.org/jira/browse/HADOOP-1602
Project: Hadoop
Issue Type: Bug
Components: mapred
Affects Versions: 0.13.0
Reporter: Michael Bieniosek
Priority: Minor
While working on HADOOP-1524, I noticed that TaskLog.java pulls the entire userlog into a giant byte[] and returns the byte[]. This won't work well for large logs. TaskLog should return an InputStream instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-1602) TaskLog.java buffers entire task
userlog in memory
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley resolved HADOOP-1602.
-----------------------------------
Resolution: Duplicate
Fix Version/s: 0.14.0
Fixed as part of HADOOP-1553.
> TaskLog.java buffers entire task userlog in memory
> --------------------------------------------------
>
> Key: HADOOP-1602
> URL: https://issues.apache.org/jira/browse/HADOOP-1602
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.13.0
> Reporter: Michael Bieniosek
> Assignee: Owen O'Malley
> Priority: Minor
> Fix For: 0.14.0
>
>
> While working on HADOOP-1524, I noticed that TaskLog.Reader.fetchAll() pulls the entire userlog into a giant byte[] and returns the byte[]. This won't work well for large logs. TaskLog should return an InputStream instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-1602) TaskLog.java buffers entire task
userlog in memory
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley reassigned HADOOP-1602:
-------------------------------------
Assignee: Owen O'Malley
> TaskLog.java buffers entire task userlog in memory
> --------------------------------------------------
>
> Key: HADOOP-1602
> URL: https://issues.apache.org/jira/browse/HADOOP-1602
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.13.0
> Reporter: Michael Bieniosek
> Assignee: Owen O'Malley
> Priority: Minor
>
> While working on HADOOP-1524, I noticed that TaskLog.Reader.fetchAll() pulls the entire userlog into a giant byte[] and returns the byte[]. This won't work well for large logs. TaskLog should return an InputStream instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1602) TaskLog.java buffers entire task
userlog in memory
Posted by "Michael Bieniosek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bieniosek updated HADOOP-1602:
--------------------------------------
Description: While working on HADOOP-1524, I noticed that TaskLog.Reader.fetchAll() pulls the entire userlog into a giant byte[] and returns the byte[]. This won't work well for large logs. TaskLog should return an InputStream instead. (was: While working on HADOOP-1524, I noticed that TaskLog.java pulls the entire userlog into a giant byte[] and returns the byte[]. This won't work well for large logs. TaskLog should return an InputStream instead.)
> TaskLog.java buffers entire task userlog in memory
> --------------------------------------------------
>
> Key: HADOOP-1602
> URL: https://issues.apache.org/jira/browse/HADOOP-1602
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.13.0
> Reporter: Michael Bieniosek
> Priority: Minor
>
> While working on HADOOP-1524, I noticed that TaskLog.Reader.fetchAll() pulls the entire userlog into a giant byte[] and returns the byte[]. This won't work well for large logs. TaskLog should return an InputStream instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.