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 2007/03/28 23:15:25 UTC
[jira] Created: (HADOOP-1177) Lack of logging of exceptions in
MapOutputLocation.getFile
Lack of logging of exceptions in MapOutputLocation.getFile
----------------------------------------------------------
Key: HADOOP-1177
URL: https://issues.apache.org/jira/browse/HADOOP-1177
Project: Hadoop
Issue Type: Bug
Components: mapred
Reporter: Owen O'Malley
Assigned To: Devaraj Das
Fix For: 0.12.3
The current implementation of MapOutputLocation.getFile effectively catches all IOExceptions and returns null. This hides what is going wrong and makes it very hard to diagnose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1177) Lack of logging of exceptions in
MapOutputLocation.getFile
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-1177:
--------------------------------
Attachment: 1177.patch
Good catch, Owen. Patch attached .
> Lack of logging of exceptions in MapOutputLocation.getFile
> ----------------------------------------------------------
>
> Key: HADOOP-1177
> URL: https://issues.apache.org/jira/browse/HADOOP-1177
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Owen O'Malley
> Assigned To: Devaraj Das
> Fix For: 0.12.3
>
> Attachments: 1177.patch
>
>
> The current implementation of MapOutputLocation.getFile effectively catches all IOExceptions and returns null. This hides what is going wrong and makes it very hard to diagnose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1177) Lack of logging of exceptions in
MapOutputLocation.getFile
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485174 ]
Hadoop QA commented on HADOOP-1177:
-----------------------------------
+1, because http://issues.apache.org/jira/secure/attachment/12354511/1177.patch applied and successfully tested against trunk revision http://svn.apache.org/repos/asf/lucene/hadoop/trunk/523072. Results are at http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch
> Lack of logging of exceptions in MapOutputLocation.getFile
> ----------------------------------------------------------
>
> Key: HADOOP-1177
> URL: https://issues.apache.org/jira/browse/HADOOP-1177
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Owen O'Malley
> Assigned To: Devaraj Das
> Fix For: 0.12.3
>
> Attachments: 1177.patch
>
>
> The current implementation of MapOutputLocation.getFile effectively catches all IOExceptions and returns null. This hides what is going wrong and makes it very hard to diagnose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1177) Lack of logging of exceptions in
MapOutputLocation.getFile
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485479 ]
Hadoop QA commented on HADOOP-1177:
-----------------------------------
Integrated in Hadoop-Nightly #41 (See http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/41/)
> Lack of logging of exceptions in MapOutputLocation.getFile
> ----------------------------------------------------------
>
> Key: HADOOP-1177
> URL: https://issues.apache.org/jira/browse/HADOOP-1177
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Owen O'Malley
> Assigned To: Devaraj Das
> Fix For: 0.12.3
>
> Attachments: 1177.patch
>
>
> The current implementation of MapOutputLocation.getFile effectively catches all IOExceptions and returns null. This hides what is going wrong and makes it very hard to diagnose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1177) Lack of logging of exceptions in
MapOutputLocation.getFile
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-1177:
--------------------------------
Status: Patch Available (was: Open)
> Lack of logging of exceptions in MapOutputLocation.getFile
> ----------------------------------------------------------
>
> Key: HADOOP-1177
> URL: https://issues.apache.org/jira/browse/HADOOP-1177
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Owen O'Malley
> Assigned To: Devaraj Das
> Fix For: 0.12.3
>
> Attachments: 1177.patch
>
>
> The current implementation of MapOutputLocation.getFile effectively catches all IOExceptions and returns null. This hides what is going wrong and makes it very hard to diagnose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1177) Lack of logging of exceptions in
MapOutputLocation.getFile
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-1177:
------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I've just committed this. Thanks Devaraj!
> Lack of logging of exceptions in MapOutputLocation.getFile
> ----------------------------------------------------------
>
> Key: HADOOP-1177
> URL: https://issues.apache.org/jira/browse/HADOOP-1177
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Owen O'Malley
> Assigned To: Devaraj Das
> Fix For: 0.12.3
>
> Attachments: 1177.patch
>
>
> The current implementation of MapOutputLocation.getFile effectively catches all IOExceptions and returns null. This hides what is going wrong and makes it very hard to diagnose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.