hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5140) setting fs.default.name to an invalid URI format kills init thread in JobTracker
Date Fri, 22 May 2009 20:22:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712237#action_12712237
] 

Steve Loughran commented on HADOOP-5140:
----------------------------------------

This is only loosely related to HADOOP-5687. That was bad failing on invalid fs.default.name
values in the NN. This is bad handling of the (correct) failure to parse bad fs.default.name
values. The changes I'm doing for HADOOP-5687 will change the error message to be more helpful,
but you still need that code in the JobInitThread to catch the bad value during the cleanup
process, which is what is apparently happening here.

> setting fs.default.name to an invalid URI format kills init thread in JobTracker
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-5140
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5140
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: sam rash
>            Priority: Minor
>
> If you set fs.default.name in a JobConf object to something that causes java.net.URI
to throw an IllegalArgumentException, the job not only fails initalization, but kills the
JobInitThread

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message