hadoop-common-issues 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-6614) RunJar should provide more diags when it can't create a temp file
Date Tue, 02 Aug 2011 10:10:27 GMT

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

Steve Loughran commented on HADOOP-6614:
----------------------------------------

that latter problem looks like an OS/X case quirk; there's two files with the same (case insensitive)
name in the FS, the File.getParent() probably uses strings and path separators and not inodes
to determine the parent, so it fails as the search finds the file and not the directory.

The PICO-299 issue is related to Visa, but NTFS has different naming logic: if you save a
file for which there is already a file of the same name (case insensitively tested), the saved
file gets the name of the file that already exists, even if its case was different.

Perhaps the <jar> task or Maven equivalent could be set up to warn on these problems,
as they are clearly recurrent. 

> RunJar should provide more diags when it can't create a temp file
> -----------------------------------------------------------------
>
>                 Key: HADOOP-6614
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6614
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 0.22.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> When you see a stack trace about permissions, it is better if the trace included the
file/directory at fault:
> {code}
> Exception in thread "main" java.io.IOException: Permission denied
> 	at java.io.UnixFileSystem.createFileExclusively(Native Method)
> 	at java.io.File.checkAndCreate(File.java:1704)
> 	at java.io.File.createTempFile(File.java:1792)
> 	at org.apache.hadoop.util.RunJar.main(RunJar.java:147)
> {code}
> As it is, you need to go into the code, discover that it's {{${hadoop.tmp.dir}/hadoop-unjar}},
but you need to know the value of hadoop.tmp.dir to really find out what the problem is.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message