[jira] [Created] (HADOOP-9062) hadoop-env.cmd overwrites the value of *_OPTS set before install
Ganeshan Iyer created HADOOP-9062: - Summary: hadoop-env.cmd overwrites the value of *_OPTS set before install Key: HADOOP-9062 URL: https://issues.apache.org/jira/browse/HADOOP-9062 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Environment: Windows Reporter: Ganeshan Iyer Fix For: 1-win The values of the following environment variables are overwritten in the hadoop-env.cmd file. HADOOP_NAMENODE_OPTS HADOOP_SECONDARYNAMENODE_OPTS HADOOP_DATANODE_OPTS HADOOP_BALANCER_OPTS HADOOP_JOBTRACKER_OPTS HADOOP_TASKTRACKER_OPTS This blocks us from using these variables for setting other properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9062) hadoop-env.cmd overwrites the value of *_OPTS set before install
[ https://issues.apache.org/jira/browse/HADOOP-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganeshan Iyer updated HADOOP-9062: -- Attachment: HADOOP-9062.1-win.001.patch Attaching patch that appends the values instead of overwriting. hadoop-env.cmd overwrites the value of *_OPTS set before install Key: HADOOP-9062 URL: https://issues.apache.org/jira/browse/HADOOP-9062 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Environment: Windows Reporter: Ganeshan Iyer Fix For: 1-win Attachments: HADOOP-9062.1-win.001.patch The values of the following environment variables are overwritten in the hadoop-env.cmd file. HADOOP_NAMENODE_OPTS HADOOP_SECONDARYNAMENODE_OPTS HADOOP_DATANODE_OPTS HADOOP_BALANCER_OPTS HADOOP_JOBTRACKER_OPTS HADOOP_TASKTRACKER_OPTS This blocks us from using these variables for setting other properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9062) hadoop-env.cmd overwrites the value of *_OPTS set before install
[ https://issues.apache.org/jira/browse/HADOOP-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganeshan Iyer updated HADOOP-9062: -- Target Version/s: 1-win Status: Patch Available (was: Open) hadoop-env.cmd overwrites the value of *_OPTS set before install Key: HADOOP-9062 URL: https://issues.apache.org/jira/browse/HADOOP-9062 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Environment: Windows Reporter: Ganeshan Iyer Fix For: 1-win Attachments: HADOOP-9062.1-win.001.patch The values of the following environment variables are overwritten in the hadoop-env.cmd file. HADOOP_NAMENODE_OPTS HADOOP_SECONDARYNAMENODE_OPTS HADOOP_DATANODE_OPTS HADOOP_BALANCER_OPTS HADOOP_JOBTRACKER_OPTS HADOOP_TASKTRACKER_OPTS This blocks us from using these variables for setting other properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9062) hadoop-env.cmd overwrites the value of *_OPTS set before install
[
https://issues.apache.org/jira/browse/HADOOP-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500106#comment-13500106
]
Hadoop QA commented on HADOOP-9062:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12554137/HADOOP-9062.1-win.001.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1769//console
This message is automatically generated.
hadoop-env.cmd overwrites the value of *_OPTS set before install
Key: HADOOP-9062
URL: https://issues.apache.org/jira/browse/HADOOP-9062
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 1-win
Environment: Windows
Reporter: Ganeshan Iyer
Fix For: 1-win
Attachments: HADOOP-9062.1-win.001.patch
The values of the following environment variables are overwritten in the
hadoop-env.cmd file.
HADOOP_NAMENODE_OPTS
HADOOP_SECONDARYNAMENODE_OPTS
HADOOP_DATANODE_OPTS
HADOOP_BALANCER_OPTS
HADOOP_JOBTRACKER_OPTS
HADOOP_TASKTRACKER_OPTS
This blocks us from using these variables for setting other properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9041) FileSystem initialization can go into infinite loop
[ https://issues.apache.org/jira/browse/HADOOP-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500240#comment-13500240 ] Tom White commented on HADOOP-9041: --- Can you convert the Groovy test into a JUnit test so we have a regression test? FileSystem initialization can go into infinite loop --- Key: HADOOP-9041 URL: https://issues.apache.org/jira/browse/HADOOP-9041 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 2.0.2-alpha Reporter: Radim Kolar Assignee: Yanbo Liang Priority: Critical Attachments: fstest.groovy, HADOOP-9041.patch, HADOOP-9041.patch More information is there: https://jira.springsource.org/browse/SHDP-111 Referenced source code from example is: https://github.com/SpringSource/spring-hadoop/blob/master/src/main/java/org/springframework/data/hadoop/configuration/ConfigurationFactoryBean.java from isolating that cause it looks like if you register: org.apache.hadoop.fs.FsUrlStreamHandlerFactory before calling FileSystem.loadFileSystems() then it goes into infinite loop. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9049) DelegationTokenRenewer needs to be Singleton and FileSystems should register/deregister to/from.
[
https://issues.apache.org/jira/browse/HADOOP-9049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500310#comment-13500310
]
Daryn Sharp commented on HADOOP-9049:
-
+1 But I'd suggest canceling the token in {{removeRenewAction}}. Hftp
webhdfs only register tokens for renewal that are implicitly created for
internal use. Since they aren't cancelled, it causes a bunch of defunct tokens
to clog the NN until they expire. If you want to fix it on another jira, I'm
fine with that.
DelegationTokenRenewer needs to be Singleton and FileSystems should
register/deregister to/from.
Key: HADOOP-9049
URL: https://issues.apache.org/jira/browse/HADOOP-9049
Project: Hadoop Common
Issue Type: Bug
Components: security
Affects Versions: 2.0.2-alpha
Reporter: Karthik Kambatla
Assignee: Karthik Kambatla
Attachments: hadoop-9049.patch, hadoop-9049.patch
Currently, DelegationTokenRenewer is not singleton.
Each filesystem using it spawns its own DelegationTokenRenewer. Also, they
don't stop the Renewer leading to other problems.
A single DelegationTokenRenewer should be sufficient for all FileSystems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9054) Add AuthenticationHandler that uses Kerberos but allows for an alternate form of authentication for browsers
[ https://issues.apache.org/jira/browse/HADOOP-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500368#comment-13500368 ] Robert Kanter commented on HADOOP-9054: --- This is to make it easier for others to implement their own AuthenticationHandler that uses Kerberos in some cases and their own authentication mechanism (which they have to implement themselves; I'll be making an abstract class) in other cases (i.e. browser access). So, I don't think I'd call it chain-able, but maybe mixed. Add AuthenticationHandler that uses Kerberos but allows for an alternate form of authentication for browsers Key: HADOOP-9054 URL: https://issues.apache.org/jira/browse/HADOOP-9054 Project: Hadoop Common Issue Type: New Feature Components: security Reporter: Robert Kanter Assignee: Robert Kanter Fix For: 1.2.0, 2.0.3-alpha It would be useful for some Oozie users if, when using Kerberos, that browser access to the oozie web UI could be authenticated in a different way (w/o Kerberos). This may be useful for other projects using Hadoop-Auth, so this feature is to add a new AuthenticationHandler that uses Kerberos by default, unless a browser (user-agents are configurable) is used, in which case some other form of authentication can be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9041) FileSystem initialization can go into infinite loop
[ https://issues.apache.org/jira/browse/HADOOP-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Kolar updated HADOOP-9041: Attachment: fsinit-unit.txt FileSystem initialization can go into infinite loop --- Key: HADOOP-9041 URL: https://issues.apache.org/jira/browse/HADOOP-9041 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 2.0.2-alpha Reporter: Radim Kolar Assignee: Yanbo Liang Priority: Critical Attachments: fsinit-unit.txt, fstest.groovy, HADOOP-9041.patch, HADOOP-9041.patch More information is there: https://jira.springsource.org/browse/SHDP-111 Referenced source code from example is: https://github.com/SpringSource/spring-hadoop/blob/master/src/main/java/org/springframework/data/hadoop/configuration/ConfigurationFactoryBean.java from isolating that cause it looks like if you register: org.apache.hadoop.fs.FsUrlStreamHandlerFactory before calling FileSystem.loadFileSystems() then it goes into infinite loop. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9063) enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil
Ivan A. Veselovsky created HADOOP-9063: -- Summary: enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil Key: HADOOP-9063 URL: https://issues.apache.org/jira/browse/HADOOP-9063 Project: Hadoop Common Issue Type: Test Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Priority: Minor Some methods of class org.apache.hadoop.fs.FileUtil are covered by unit-tests poorly or not covered at all. Enhance the coverage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9064) Augment DelegationTokenRenewer API to cancel the tokens on calls to removeRenewAction
Karthik Kambatla created HADOOP-9064:
Summary: Augment DelegationTokenRenewer API to cancel the tokens
on calls to removeRenewAction
Key: HADOOP-9064
URL: https://issues.apache.org/jira/browse/HADOOP-9064
Project: Hadoop Common
Issue Type: Bug
Components: security
Affects Versions: 2.0.2-alpha
Reporter: Karthik Kambatla
Assignee: Karthik Kambatla
Post HADOOP-9049, FileSystems register with DelegationTokenRenewer (a
singleton), to renew tokens.
To avoid a bunch of defunct tokens clog the NN, we should augment the API to
{{#removeRenewAction(boolean cancel)}} and cancel the token appropriately.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9041) FileSystem initialization can go into infinite loop
[
https://issues.apache.org/jira/browse/HADOOP-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500421#comment-13500421
]
Hadoop QA commented on HADOOP-9041:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12554193/fsinit-unit.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1770//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1770//console
This message is automatically generated.
FileSystem initialization can go into infinite loop
---
Key: HADOOP-9041
URL: https://issues.apache.org/jira/browse/HADOOP-9041
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 2.0.2-alpha
Reporter: Radim Kolar
Assignee: Yanbo Liang
Priority: Critical
Attachments: fsinit-unit.txt, fstest.groovy, HADOOP-9041.patch,
HADOOP-9041.patch
More information is there: https://jira.springsource.org/browse/SHDP-111
Referenced source code from example is:
https://github.com/SpringSource/spring-hadoop/blob/master/src/main/java/org/springframework/data/hadoop/configuration/ConfigurationFactoryBean.java
from isolating that cause it looks like if you register:
org.apache.hadoop.fs.FsUrlStreamHandlerFactory before calling
FileSystem.loadFileSystems() then it goes into infinite loop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9049) DelegationTokenRenewer needs to be Singleton and FileSystems should register/deregister to/from.
[
https://issues.apache.org/jira/browse/HADOOP-9049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500425#comment-13500425
]
Karthik Kambatla commented on HADOOP-9049:
--
Hi Daryn,
Thanks for the review.
I have filed HADOOP-9064 to add canceling the token. I feel we should pass a
boolean to {{#removeRenewAction(boolean cancel)}} and cancel the token
accordingly. The filesystems can call removeRenewAction with cancel set to true.
DelegationTokenRenewer needs to be Singleton and FileSystems should
register/deregister to/from.
Key: HADOOP-9049
URL: https://issues.apache.org/jira/browse/HADOOP-9049
Project: Hadoop Common
Issue Type: Bug
Components: security
Affects Versions: 2.0.2-alpha
Reporter: Karthik Kambatla
Assignee: Karthik Kambatla
Attachments: hadoop-9049.patch, hadoop-9049.patch
Currently, DelegationTokenRenewer is not singleton.
Each filesystem using it spawns its own DelegationTokenRenewer. Also, they
don't stop the Renewer leading to other problems.
A single DelegationTokenRenewer should be sufficient for all FileSystems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7207) fs member of FSShell is not really needed
[ https://issues.apache.org/jira/browse/HADOOP-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-7207: --- Fix Version/s: 0.23.0 fs member of FSShell is not really needed - Key: HADOOP-7207 URL: https://issues.apache.org/jira/browse/HADOOP-7207 Project: Hadoop Common Issue Type: Bug Reporter: Boris Shkolnik Assignee: Boris Shkolnik Fix For: 0.23.0 Attachments: HADOOP-7207-22.patch, HADOOP-7207-2.patch, HADOOP-7207-3.patch FileSystem object should be created on demand when needed in FSShell, instead of always creating one that connects to the default FileSystem. It will also solve a problem of connecting to non-existant/non-functional default, when it is not really needed for this run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9044) add FindClass main class to provide classpath checking of installations
[ https://issues.apache.org/jira/browse/HADOOP-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500439#comment-13500439 ] Steve Loughran commented on HADOOP-9044: you are right, I just didn't have trunk in front of me. Should I do the patch for trunk? add FindClass main class to provide classpath checking of installations --- Key: HADOOP-9044 URL: https://issues.apache.org/jira/browse/HADOOP-9044 Project: Hadoop Common Issue Type: New Feature Components: util Affects Versions: 1.1.0 Reporter: Steve Loughran Assignee: Steve Loughran Priority: Minor Attachments: HADOOP-9044.patch It's useful in postflight checking of a hadoop installation to verify that classes load, especially codes with external JARs and native codecs. An entry point designed to load a named class and create an instance of that class can do this -and be invoked from any shell script or tool that does the installation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9044) add FindClass main class to provide classpath checking of installations
[ https://issues.apache.org/jira/browse/HADOOP-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500443#comment-13500443 ] Suresh Srinivas commented on HADOOP-9044: - Yes, if you do the patch for the trunk, then I will backport it to branch-1. add FindClass main class to provide classpath checking of installations --- Key: HADOOP-9044 URL: https://issues.apache.org/jira/browse/HADOOP-9044 Project: Hadoop Common Issue Type: New Feature Components: util Affects Versions: 1.1.0 Reporter: Steve Loughran Assignee: Steve Loughran Priority: Minor Attachments: HADOOP-9044.patch It's useful in postflight checking of a hadoop installation to verify that classes load, especially codes with external JARs and native codecs. An entry point designed to load a named class and create an instance of that class can do this -and be invoked from any shell script or tool that does the installation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8589) ViewFs tests fail when tests and home dirs are nested
[
https://issues.apache.org/jira/browse/HADOOP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500451#comment-13500451
]
Andrey Klochkov commented on HADOOP-8589:
-
The reported issue is still not fixed. If tests are run on a Jenkins master
node, with Jenkins using it's default home (/var/lib/jenkins), view fs tests
fail with the error given in the description of this Jira.
ViewFs tests fail when tests and home dirs are nested
-
Key: HADOOP-8589
URL: https://issues.apache.org/jira/browse/HADOOP-8589
Project: Hadoop Common
Issue Type: Bug
Components: fs, test
Affects Versions: 0.23.1, 2.0.0-alpha
Reporter: Andrey Klochkov
Assignee: Sanjay Radia
Attachments: Hadoop-8589.patch, HADOOP-8589.patch, HADOOP-8589.patch,
hadoop-8589-sanjay.patch, Hadoop-8589-v2.patch, HADOOP-8859.patch
TestFSMainOperationsLocalFileSystem fails in case when the test root
directory is under the user's home directory, and the user's home dir is
deeper than 2 levels from /. This happens with the default 1-node
installation of Jenkins.
This is the failure log:
{code}
org.apache.hadoop.fs.FileAlreadyExistsException: Path /var already exists as
dir; cannot create link here
at org.apache.hadoop.fs.viewfs.InodeTree.createLink(InodeTree.java:244)
at org.apache.hadoop.fs.viewfs.InodeTree.init(InodeTree.java:334)
at
org.apache.hadoop.fs.viewfs.ViewFileSystem$1.init(ViewFileSystem.java:167)
at
org.apache.hadoop.fs.viewfs.ViewFileSystem.initialize(ViewFileSystem.java:167)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2094)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:79)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2128)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2110)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:290)
at
org.apache.hadoop.fs.viewfs.ViewFileSystemTestSetup.setupForViewFileSystem(ViewFileSystemTestSetup.java:76)
at
org.apache.hadoop.fs.viewfs.TestFSMainOperationsLocalFileSystem.setUp(TestFSMainOperationsLocalFileSystem.java:40)
...
Standard Output
2012-07-11 22:07:20,239 INFO mortbay.log (Slf4jLog.java:info(67)) - Home dir
base /var/lib
{code}
The reason for the failure is that the code tries to mount links for both
/var and /var/lib, and it fails for the 2nd one as the /var is mounted
already.
The fix was provided in HADOOP-8036 but later it was reverted in HADOOP-8129.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9061) Java6+Windows does not work well with symlinks
[
https://issues.apache.org/jira/browse/HADOOP-9061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500453#comment-13500453
]
Colin Patrick McCabe commented on HADOOP-9061:
--
One way to handle this would be to disable symlinks on Windows unless JDK7 is
present. Another way would be a symlink-aware implementation of operations
like {{File#renameTo}} on JDK6 and earlier. This would have to be JNI, I
think, and could be done in {{libhadoop.so}}.
Java6+Windows does not work well with symlinks
--
Key: HADOOP-9061
URL: https://issues.apache.org/jira/browse/HADOOP-9061
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 1-win
Reporter: Ivan Mitic
Assignee: Ivan Mitic
We’ve seen multiple problems with file operations on symbolic links on Java6
on Windows. Specifically:
- File#length returns zero on symbolic links
- File#renameTo renames the target, not the symlink
Problematic scenarios are mainly related to symlinks created for dist cache.
Java7 does not have above problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9054) Add AuthenticationHandler that uses Kerberos but allows for an alternate form of authentication for browsers
[ https://issues.apache.org/jira/browse/HADOOP-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500456#comment-13500456 ] Allen Wittenauer commented on HADOOP-9054: -- Maybe this is dumb question but... why does Apache Hadoop need to provide this code, given that this is already pluggable allowing users to provide their own bits now? In other words, if they already have this need to provide two (essentially) incompatible mechanisms what prevents them? Add AuthenticationHandler that uses Kerberos but allows for an alternate form of authentication for browsers Key: HADOOP-9054 URL: https://issues.apache.org/jira/browse/HADOOP-9054 Project: Hadoop Common Issue Type: New Feature Components: security Reporter: Robert Kanter Assignee: Robert Kanter Fix For: 1.2.0, 2.0.3-alpha It would be useful for some Oozie users if, when using Kerberos, that browser access to the oozie web UI could be authenticated in a different way (w/o Kerberos). This may be useful for other projects using Hadoop-Auth, so this feature is to add a new AuthenticationHandler that uses Kerberos by default, unless a browser (user-agents are configurable) is used, in which case some other form of authentication can be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8958) ViewFs:Non absolute mount name failures when running multiple tests on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500460#comment-13500460 ] Sanjay Radia commented on HADOOP-8958: -- Chris, in windows, would it be safe to assume the mount point is /x:/path? If so then isn't it sufficient put a simple if-windows and then assume that the path does have the drive-letter. ViewFs:Non absolute mount name failures when running multiple tests on Windows -- Key: HADOOP-8958 URL: https://issues.apache.org/jira/browse/HADOOP-8958 Project: Hadoop Common Issue Type: Bug Components: viewfs Affects Versions: trunk-win Reporter: Chris Nauroth Assignee: Chris Nauroth Attachments: HADOOP-8958.patch This appears to be an issue with parsing a Windows-specific path. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9054) Add AuthenticationHandler that uses Kerberos but allows for an alternate form of authentication for browsers
[ https://issues.apache.org/jira/browse/HADOOP-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500462#comment-13500462 ] Robert Kanter commented on HADOOP-9054: --- I suppose there's nothing preventing them from doing it themselves, but this should make it easier as they won't have to worry about Kerberos or managing the two authentication mechanisms; all they'd have to do is implement one method to authenticate using their mechanism and get the other stuff for free from this code. Add AuthenticationHandler that uses Kerberos but allows for an alternate form of authentication for browsers Key: HADOOP-9054 URL: https://issues.apache.org/jira/browse/HADOOP-9054 Project: Hadoop Common Issue Type: New Feature Components: security Reporter: Robert Kanter Assignee: Robert Kanter Fix For: 1.2.0, 2.0.3-alpha It would be useful for some Oozie users if, when using Kerberos, that browser access to the oozie web UI could be authenticated in a different way (w/o Kerberos). This may be useful for other projects using Hadoop-Auth, so this feature is to add a new AuthenticationHandler that uses Kerberos by default, unless a browser (user-agents are configurable) is used, in which case some other form of authentication can be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8589) ViewFs tests fail when tests and home dirs are nested
[
https://issues.apache.org/jira/browse/HADOOP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500470#comment-13500470
]
Andrey Klochkov commented on HADOOP-8589:
-
Apparently it's fixed in trunk only, while the target versions field points
to 3.x/0.23/2.x. Can it be backported to 2.x/0.23 as well?
ViewFs tests fail when tests and home dirs are nested
-
Key: HADOOP-8589
URL: https://issues.apache.org/jira/browse/HADOOP-8589
Project: Hadoop Common
Issue Type: Bug
Components: fs, test
Affects Versions: 0.23.1, 2.0.0-alpha
Reporter: Andrey Klochkov
Assignee: Sanjay Radia
Attachments: Hadoop-8589.patch, HADOOP-8589.patch, HADOOP-8589.patch,
hadoop-8589-sanjay.patch, Hadoop-8589-v2.patch, HADOOP-8859.patch
TestFSMainOperationsLocalFileSystem fails in case when the test root
directory is under the user's home directory, and the user's home dir is
deeper than 2 levels from /. This happens with the default 1-node
installation of Jenkins.
This is the failure log:
{code}
org.apache.hadoop.fs.FileAlreadyExistsException: Path /var already exists as
dir; cannot create link here
at org.apache.hadoop.fs.viewfs.InodeTree.createLink(InodeTree.java:244)
at org.apache.hadoop.fs.viewfs.InodeTree.init(InodeTree.java:334)
at
org.apache.hadoop.fs.viewfs.ViewFileSystem$1.init(ViewFileSystem.java:167)
at
org.apache.hadoop.fs.viewfs.ViewFileSystem.initialize(ViewFileSystem.java:167)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2094)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:79)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2128)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2110)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:290)
at
org.apache.hadoop.fs.viewfs.ViewFileSystemTestSetup.setupForViewFileSystem(ViewFileSystemTestSetup.java:76)
at
org.apache.hadoop.fs.viewfs.TestFSMainOperationsLocalFileSystem.setUp(TestFSMainOperationsLocalFileSystem.java:40)
...
Standard Output
2012-07-11 22:07:20,239 INFO mortbay.log (Slf4jLog.java:info(67)) - Home dir
base /var/lib
{code}
The reason for the failure is that the code tries to mount links for both
/var and /var/lib, and it fails for the 2nd one as the /var is mounted
already.
The fix was provided in HADOOP-8036 but later it was reverted in HADOOP-8129.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9041) FileSystem initialization can go into infinite loop
[ https://issues.apache.org/jira/browse/HADOOP-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500487#comment-13500487 ] Alejandro Abdelnur commented on HADOOP-9041: Yanbo Liang, thanks for the detailed explanation, yes it makes sense. As a side question, do you know why this has not been observed before? Also, as Tom said the testcase should be junit based. FileSystem initialization can go into infinite loop --- Key: HADOOP-9041 URL: https://issues.apache.org/jira/browse/HADOOP-9041 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 2.0.2-alpha Reporter: Radim Kolar Assignee: Yanbo Liang Priority: Critical Attachments: fsinit-unit.txt, fstest.groovy, HADOOP-9041.patch, HADOOP-9041.patch More information is there: https://jira.springsource.org/browse/SHDP-111 Referenced source code from example is: https://github.com/SpringSource/spring-hadoop/blob/master/src/main/java/org/springframework/data/hadoop/configuration/ConfigurationFactoryBean.java from isolating that cause it looks like if you register: org.apache.hadoop.fs.FsUrlStreamHandlerFactory before calling FileSystem.loadFileSystems() then it goes into infinite loop. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8991) Add support for SASL PLAIN authentication
[
https://issues.apache.org/jira/browse/HADOOP-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-8991:
Attachment: HADOOP-8991.patch
Add sasl PLAIN security value. Add client and server callbacks for PLAIN.
Tried to localize the setting of the UGI auth type closer to where it's
constructed to ensure the correct real/effective user gets sets.
Add support for SASL PLAIN authentication
-
Key: HADOOP-8991
URL: https://issues.apache.org/jira/browse/HADOOP-8991
Project: Hadoop Common
Issue Type: Sub-task
Components: ipc
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-8991.patch
Adding SASL PLAIN auth will allow {{isSecurityEnabled}} to mean SASL is
active instead of only meaning kerberos is enabled. SASL will always require
tokens. PLAIN will be the same as SIMPLE, with the added requirement of
tokens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8991) Add support for SASL PLAIN authentication
[
https://issues.apache.org/jira/browse/HADOOP-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-8991:
Status: Patch Available (was: Open)
Add support for SASL PLAIN authentication
-
Key: HADOOP-8991
URL: https://issues.apache.org/jira/browse/HADOOP-8991
Project: Hadoop Common
Issue Type: Sub-task
Components: ipc
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-8991.patch
Adding SASL PLAIN auth will allow {{isSecurityEnabled}} to mean SASL is
active instead of only meaning kerberos is enabled. SASL will always require
tokens. PLAIN will be the same as SIMPLE, with the added requirement of
tokens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9063) enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil
[ https://issues.apache.org/jira/browse/HADOOP-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan A. Veselovsky updated HADOOP-9063: --- Status: Patch Available (was: Open) enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil - Key: HADOOP-9063 URL: https://issues.apache.org/jira/browse/HADOOP-9063 Project: Hadoop Common Issue Type: Test Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Priority: Minor Attachments: HADOOP-9063.patch Some methods of class org.apache.hadoop.fs.FileUtil are covered by unit-tests poorly or not covered at all. Enhance the coverage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9063) enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil
[ https://issues.apache.org/jira/browse/HADOOP-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan A. Veselovsky updated HADOOP-9063: --- Attachment: HADOOP-9063.patch provided several more tests for FileUtil class. enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil - Key: HADOOP-9063 URL: https://issues.apache.org/jira/browse/HADOOP-9063 Project: Hadoop Common Issue Type: Test Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Priority: Minor Attachments: HADOOP-9063.patch Some methods of class org.apache.hadoop.fs.FileUtil are covered by unit-tests poorly or not covered at all. Enhance the coverage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-6616) Improve documentation for rack awareness
[ https://issues.apache.org/jira/browse/HADOOP-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500522#comment-13500522 ] Jakob Homan commented on HADOOP-6616: - +1. Looks good. Verified generated html (working around HADOOP-8810). Committing. Improve documentation for rack awareness Key: HADOOP-6616 URL: https://issues.apache.org/jira/browse/HADOOP-6616 Project: Hadoop Common Issue Type: Improvement Components: documentation Reporter: Jeff Hammerbacher Assignee: Adam Faris Labels: newbie Attachments: hadoop-6616.patch, hadoop-6616.patch.2, hadoop-6616.patch.3, hadoop-6616.patch.4 The current documentation for rack awareness (http://hadoop.apache.org/common/docs/r0.20.0/cluster_setup.html#Hadoop+Rack+Awareness) should be augmented to include a sample script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-6616) Improve documentation for rack awareness
[ https://issues.apache.org/jira/browse/HADOOP-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated HADOOP-6616: Fix Version/s: 3.0.0 Hadoop Flags: Reviewed Improve documentation for rack awareness Key: HADOOP-6616 URL: https://issues.apache.org/jira/browse/HADOOP-6616 Project: Hadoop Common Issue Type: Improvement Components: documentation Reporter: Jeff Hammerbacher Assignee: Adam Faris Labels: newbie Fix For: 3.0.0 Attachments: hadoop-6616.patch, hadoop-6616.patch.2, hadoop-6616.patch.3, hadoop-6616.patch.4 The current documentation for rack awareness (http://hadoop.apache.org/common/docs/r0.20.0/cluster_setup.html#Hadoop+Rack+Awareness) should be augmented to include a sample script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-6616) Improve documentation for rack awareness
[ https://issues.apache.org/jira/browse/HADOOP-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated HADOOP-6616: Resolution: Fixed Status: Resolved (was: Patch Available) I've committed this. Resolving as fixed. Thanks, Adam! Improve documentation for rack awareness Key: HADOOP-6616 URL: https://issues.apache.org/jira/browse/HADOOP-6616 Project: Hadoop Common Issue Type: Improvement Components: documentation Reporter: Jeff Hammerbacher Assignee: Adam Faris Labels: newbie Fix For: 3.0.0 Attachments: hadoop-6616.patch, hadoop-6616.patch.2, hadoop-6616.patch.3, hadoop-6616.patch.4 The current documentation for rack awareness (http://hadoop.apache.org/common/docs/r0.20.0/cluster_setup.html#Hadoop+Rack+Awareness) should be augmented to include a sample script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8991) Add support for SASL PLAIN authentication
[
https://issues.apache.org/jira/browse/HADOOP-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500549#comment-13500549
]
Hadoop QA commented on HADOOP-8991:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12554212/HADOOP-8991.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common:
org.apache.hadoop.security.TestDoAsEffectiveUser
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1771//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1771//console
This message is automatically generated.
Add support for SASL PLAIN authentication
-
Key: HADOOP-8991
URL: https://issues.apache.org/jira/browse/HADOOP-8991
Project: Hadoop Common
Issue Type: Sub-task
Components: ipc
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-8991.patch
Adding SASL PLAIN auth will allow {{isSecurityEnabled}} to mean SASL is
active instead of only meaning kerberos is enabled. SASL will always require
tokens. PLAIN will be the same as SIMPLE, with the added requirement of
tokens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-6616) Improve documentation for rack awareness
[ https://issues.apache.org/jira/browse/HADOOP-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500546#comment-13500546 ] Hudson commented on HADOOP-6616: Integrated in Hadoop-trunk-Commit #3047 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3047/]) HADOOP-6616. Improve documentation for rack awareness. Contributed by Adam Faris. (Revision 1411359) Result = SUCCESS jghoman : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1411359 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/docs/src/documentation/content/xdocs/cluster_setup.xml Improve documentation for rack awareness Key: HADOOP-6616 URL: https://issues.apache.org/jira/browse/HADOOP-6616 Project: Hadoop Common Issue Type: Improvement Components: documentation Reporter: Jeff Hammerbacher Assignee: Adam Faris Labels: newbie Fix For: 3.0.0 Attachments: hadoop-6616.patch, hadoop-6616.patch.2, hadoop-6616.patch.3, hadoop-6616.patch.4 The current documentation for rack awareness (http://hadoop.apache.org/common/docs/r0.20.0/cluster_setup.html#Hadoop+Rack+Awareness) should be augmented to include a sample script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9063) enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil
[
https://issues.apache.org/jira/browse/HADOOP-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500571#comment-13500571
]
Hadoop QA commented on HADOOP-9063:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12554214/HADOOP-9063.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1772//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1772//console
This message is automatically generated.
enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil
-
Key: HADOOP-9063
URL: https://issues.apache.org/jira/browse/HADOOP-9063
Project: Hadoop Common
Issue Type: Test
Reporter: Ivan A. Veselovsky
Assignee: Ivan A. Veselovsky
Priority: Minor
Attachments: HADOOP-9063.patch
Some methods of class org.apache.hadoop.fs.FileUtil are covered by unit-tests
poorly or not covered at all. Enhance the coverage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8589) ViewFs tests fail when tests and home dirs are nested
[
https://issues.apache.org/jira/browse/HADOOP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8589:
Target Version/s: 2.0.3-alpha, 0.23.5 (was: 3.0.0, 0.23.4, 2.0.3-alpha)
Fix Version/s: 3.0.0
ViewFs tests fail when tests and home dirs are nested
-
Key: HADOOP-8589
URL: https://issues.apache.org/jira/browse/HADOOP-8589
Project: Hadoop Common
Issue Type: Bug
Components: fs, test
Affects Versions: 0.23.1, 2.0.0-alpha
Reporter: Andrey Klochkov
Assignee: Sanjay Radia
Fix For: 3.0.0
Attachments: Hadoop-8589.patch, HADOOP-8589.patch, HADOOP-8589.patch,
hadoop-8589-sanjay.patch, Hadoop-8589-v2.patch, HADOOP-8859.patch
TestFSMainOperationsLocalFileSystem fails in case when the test root
directory is under the user's home directory, and the user's home dir is
deeper than 2 levels from /. This happens with the default 1-node
installation of Jenkins.
This is the failure log:
{code}
org.apache.hadoop.fs.FileAlreadyExistsException: Path /var already exists as
dir; cannot create link here
at org.apache.hadoop.fs.viewfs.InodeTree.createLink(InodeTree.java:244)
at org.apache.hadoop.fs.viewfs.InodeTree.init(InodeTree.java:334)
at
org.apache.hadoop.fs.viewfs.ViewFileSystem$1.init(ViewFileSystem.java:167)
at
org.apache.hadoop.fs.viewfs.ViewFileSystem.initialize(ViewFileSystem.java:167)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2094)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:79)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2128)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2110)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:290)
at
org.apache.hadoop.fs.viewfs.ViewFileSystemTestSetup.setupForViewFileSystem(ViewFileSystemTestSetup.java:76)
at
org.apache.hadoop.fs.viewfs.TestFSMainOperationsLocalFileSystem.setUp(TestFSMainOperationsLocalFileSystem.java:40)
...
Standard Output
2012-07-11 22:07:20,239 INFO mortbay.log (Slf4jLog.java:info(67)) - Home dir
base /var/lib
{code}
The reason for the failure is that the code tries to mount links for both
/var and /var/lib, and it fails for the 2nd one as the /var is mounted
already.
The fix was provided in HADOOP-8036 but later it was reverted in HADOOP-8129.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8991) Add support for SASL PLAIN authentication
[
https://issues.apache.org/jira/browse/HADOOP-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-8991:
Attachment: HADOOP-8991.patch
{{TestDoAsEffectiveUser}} was checking that the proxy part of the ugi was being
lost. Awhile back there was a discussion about how the auth for a real vs.
effective user should be tracked. It pertained to {{JspHelper}}, proxy tokens,
and oozie. I've updated the patch to match the behavior of {{JspHelper}}.
Add support for SASL PLAIN authentication
-
Key: HADOOP-8991
URL: https://issues.apache.org/jira/browse/HADOOP-8991
Project: Hadoop Common
Issue Type: Sub-task
Components: ipc
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-8991.patch, HADOOP-8991.patch
Adding SASL PLAIN auth will allow {{isSecurityEnabled}} to mean SASL is
active instead of only meaning kerberos is enabled. SASL will always require
tokens. PLAIN will be the same as SIMPLE, with the added requirement of
tokens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9062) hadoop-env.cmd overwrites the value of *_OPTS set before install
[ https://issues.apache.org/jira/browse/HADOOP-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500835#comment-13500835 ] Bikas Saha commented on HADOOP-9062: +1 lgtm. hadoop-env.cmd overwrites the value of *_OPTS set before install Key: HADOOP-9062 URL: https://issues.apache.org/jira/browse/HADOOP-9062 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Environment: Windows Reporter: Ganeshan Iyer Fix For: 1-win Attachments: HADOOP-9062.1-win.001.patch The values of the following environment variables are overwritten in the hadoop-env.cmd file. HADOOP_NAMENODE_OPTS HADOOP_SECONDARYNAMENODE_OPTS HADOOP_DATANODE_OPTS HADOOP_BALANCER_OPTS HADOOP_JOBTRACKER_OPTS HADOOP_TASKTRACKER_OPTS This blocks us from using these variables for setting other properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
