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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2009/05/22 22:22:45 UTC

[jira] Commented: (HADOOP-5140) setting fs.default.name to an invalid URI format kills init thread in JobTracker

    [ 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.