hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "FKorning (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7682) taskTracker could not start because "Failed to set permissions" to "ttprivate to 0700"
Date Wed, 20 Jun 2012 14:57:44 GMT

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

FKorning commented on HADOOP-7682:
----------------------------------

Ismail,

You misunderstand, I haven't patched the offical 1.0.1 codebase:
I'm not an official hadoop contributor, I'm not really sure if the
developers will approve all my fixes such as adding a java.io.File
wrapper etc.

(to wit, no persons from the hadoop team, not even those who were
assigned to the various cygwin bugs, have contacted me on this).
  
what I provide are instructions for you to patch 1.0.1 yourself,
and hopefully provide guidance to the official hadoop developpers
on porting the software properly to cygwin.

and no, if you read the doc, you'll see why there is no quick
workaround, short of falling back to 0.20.  But I rather think
most people would want a 1.x, especially compiled with 64-bit.

it's not a simple code fix. you need to understand how cygwin works;
you need to customize and configure cygwin and the pre-requisite
sofware such as java, ant, ivy, maven; you need to patch scripts;
you need to patch code; you need to add brand new classes to wrap
java.io.File; you need to rebuild, reconfigure and redeploy it;

for a complete working fix, I want to port the latest version
and release the code on sourceforge, but I'm a bit busy now.



                
> taskTracker could not start because "Failed to set permissions" to "ttprivate to 0700"
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7682
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7682
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 1.0.1
>         Environment: OS:WindowsXP SP3 , Filesystem :NTFS, cygwin 1.7.9-1, jdk1.6.0_05
>            Reporter: Magic Xie
>
> ERROR org.apache.hadoop.mapred.TaskTracker:Can not start task tracker because java.io.IOException:Failed
to set permissions of path:/tmp/hadoop-cyg_server/mapred/local/ttprivate to 0700
>     at org.apache.hadoop.fs.RawLocalFileSystem.checkReturnValue(RawLocalFileSystem.java:525)
>     at org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:499)
>     at org.apache.hadoop.fs.RawLocalFileSystem.mkdirs(RawLocalFileSystem.java:318)
>     at org.apache.hadoop.fs.FilterFileSystem.mkdirs(FilterFileSystem.java:183)
>     at org.apache.hadoop.mapred.TaskTracker.initialize(TaskTracker.java:635)
>     at org.apache.hadoop.mapred.TaskTracker.(TaskTracker.java:1328)
>     at org.apache.hadoop.mapred.TaskTracker.main(TaskTracker.java:3430)
> Since hadoop0.20.203 when the TaskTracker initialize, it checks the permission(TaskTracker
Line 624) of (org.apache.hadoop.mapred.TaskTracker.TT_LOG_TMP_DIR,org.apache.hadoop.mapred.TaskTracker.TT_PRIVATE_DIR,
org.apache.hadoop.mapred.TaskTracker.TT_PRIVATE_DIR).RawLocalFileSystem(http://svn.apache.org/viewvc/hadoop/common/tags/release-0.20.203.0/src/core/org/apache/hadoop/fs/RawLocalFileSystem.java?view=markup)
call setPermission(Line 481) to deal with it, setPermission works fine on *nx, however,it
dose not alway works on windows.
> setPermission call setReadable of Java.io.File in the line 498, but according to the
Table1 below provided by oracle,setReadable(false) will always return false on windows, the
same as setExecutable(false).
> http://java.sun.com/developer/technicalArticles/J2SE/Desktop/javase6/enhancements/
> is it cause the task tracker "Failed to set permissions" to "ttprivate to 0700"?
> Hadoop 0.20.202 works fine in the same environment. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message