[jira] [Updated] (HADOOP-7173) Remove unused fstat() call from NativeIO
[ https://issues.apache.org/jira/browse/HADOOP-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7173: Fix Version/s: (was: 0.22.0) 0.22.1 > Remove unused fstat() call from NativeIO > > > Key: HADOOP-7173 > URL: https://issues.apache.org/jira/browse/HADOOP-7173 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 0.22.0 >Reporter: Todd Lipcon > Fix For: 0.22.1 > > > After HADOOP-7115, we don't need the fstat() native call or Stat class > anymore. Let's remove them to cut down on unneeded code. -- 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
[jira] [Updated] (HADOOP-6453) Hadoop wrapper script shouldn't ignore an existing JAVA_LIBRARY_PATH
[ https://issues.apache.org/jira/browse/HADOOP-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6453: Fix Version/s: (was: 0.22.0) 0.22.1 > Hadoop wrapper script shouldn't ignore an existing JAVA_LIBRARY_PATH > > > Key: HADOOP-6453 > URL: https://issues.apache.org/jira/browse/HADOOP-6453 > Project: Hadoop Common > Issue Type: Bug > Components: scripts >Affects Versions: 0.20.2, 0.21.0, 0.22.0 >Reporter: Chad Metcalf >Assignee: Matt Foley >Priority: Minor > Fix For: 0.22.1 > > Attachments: HADOOP-6453-0.20.patch, HADOOP-6453-0.20v2.patch, > HADOOP-6453-0.20v3.patch, HADOOP-6453-trunkv2.patch, > HADOOP-6453-trunkv3.patch, HADOOP-6453.trunk.patch > > > Currently the hadoop wrapper script assumes its the only place that uses > JAVA_LIBRARY_PATH and initializes it to a blank line. > JAVA_LIBRARY_PATH='' > This prevents anyone from setting this outside of the hadoop wrapper (say > hadoop-config.sh) for their own native libraries. > The fix is pretty simple. Don't initialize it to '' and append the native > libs like normal. -- 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
[jira] [Updated] (HADOOP-7308) Remove unused TaskLogAppender configurations from log4j.properties
[ https://issues.apache.org/jira/browse/HADOOP-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7308: Fix Version/s: (was: 0.22.0) 0.22.1 > Remove unused TaskLogAppender configurations from log4j.properties > -- > > Key: HADOOP-7308 > URL: https://issues.apache.org/jira/browse/HADOOP-7308 > Project: Hadoop Common > Issue Type: Improvement > Components: conf >Affects Versions: 0.22.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon > Fix For: 0.22.1 > > Attachments: hadoop-7308.txt > > > MAPREDUCE-2372 improved TaskLogAppender to no longer need as much "wiring" in > log4j.properties. There are also some old properties in there that are no > longer used (eg logsRetainHours and noKeepSplits). -- 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
[jira] [Updated] (HADOOP-7035) Document incompatible API changes between releases
[ https://issues.apache.org/jira/browse/HADOOP-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7035: Fix Version/s: (was: 0.22.0) 0.22.1 > Document incompatible API changes between releases > -- > > Key: HADOOP-7035 > URL: https://issues.apache.org/jira/browse/HADOOP-7035 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Reporter: Tom White >Assignee: Tom White >Priority: Blocker > Fix For: 0.22.1 > > Attachments: apicheck-hadoop-0.20.203.0-0.20.204.0.txt, > apicheck-hadoop-0.21.0-0.22.0-SNAPSHOT.txt, jdiff-with-previous-release.sh, > jdiff-with-previous-release.sh > > > We can use JDiff to generate a list of incompatible changes for each release. > See > https://issues.apache.org/jira/browse/HADOOP-6668?focusedCommentId=12860017&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12860017 -- 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
[jira] [Updated] (HADOOP-7338) LocalDirAllocator improvements for MR-2178
[ https://issues.apache.org/jira/browse/HADOOP-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7338: Fix Version/s: (was: 0.22.0) 0.22.1 > LocalDirAllocator improvements for MR-2178 > -- > > Key: HADOOP-7338 > URL: https://issues.apache.org/jira/browse/HADOOP-7338 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 0.22.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon > Fix For: 0.22.1 > > Attachments: hadoop-7338.txt > > > These are some changes that come from the following yahoo-merge commit, > necessary for MAPREDUCE-2178 to build. > commit 446e41f2424ddc866770cda677450c18feeb597f > Author: Chris Douglas > Date: Sun Oct 3 02:00:15 2010 -0700 > > Apply y201 to trunk > > git-svn-id: > https://svn.apache.org/repos/asf/hadoop/common/branches/yahoo-merge@1079151 > 13f79535-47bb-0310-9956-ffa450edef68 -- 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
[jira] [Updated] (HADOOP-7730) Allow TestCLI to be run against a cluster
[ https://issues.apache.org/jira/browse/HADOOP-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7730: Fix Version/s: (was: 0.22.0) 0.22.1 > Allow TestCLI to be run against a cluster > - > > Key: HADOOP-7730 > URL: https://issues.apache.org/jira/browse/HADOOP-7730 > Project: Hadoop Common > Issue Type: Test > Components: test >Affects Versions: 0.20.205.0, 0.22.0 >Reporter: Konstantin Boudnik >Assignee: Konstantin Boudnik > Fix For: 0.22.1 > > Attachments: HADOOP-7730.patch, HADOOP-7730.trunk.patch, > HADOOP-7730.trunk.patch > > > Use the same CLI test to test cluster bits (see HDFS-1762 for more info) -- 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
[jira] [Updated] (HADOOP-7648) Update date from 2009 to 2011
[ https://issues.apache.org/jira/browse/HADOOP-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7648: Fix Version/s: (was: 0.22.0) 0.22.1 > Update date from 2009 to 2011 > - > > Key: HADOOP-7648 > URL: https://issues.apache.org/jira/browse/HADOOP-7648 > Project: Hadoop Common > Issue Type: Bug > Components: build, documentation >Affects Versions: 0.22.0 >Reporter: Joep Rottinghuis > Fix For: 0.22.1 > > > Build files contains year parameter that shows up in the UI. > Some of the documentation has 2009 copyrights on them. -- 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
[jira] [Updated] (HADOOP-7332) Deadlock in IPC
[ https://issues.apache.org/jira/browse/HADOOP-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7332: Fix Version/s: (was: 0.22.0) 0.22.1 > Deadlock in IPC > --- > > Key: HADOOP-7332 > URL: https://issues.apache.org/jira/browse/HADOOP-7332 > Project: Hadoop Common > Issue Type: Bug > Components: ipc >Affects Versions: 0.22.0 >Reporter: Todd Lipcon > Fix For: 0.22.1 > > > Saw this during a run of TestIPC on 0.22 branch: > [junit] Java stack information for the threads listed above: > [junit] === > [junit] "IPC Client (47) connection to /0:0:0:0:0:0:0:0:48853 from an > unknown user": > [junit] at > org.apache.hadoop.ipc.Client$ParallelResults.callComplete(Client.java:879) > [junit] - waiting to lock <0xf599ef88> (a > org.apache.hadoop.ipc.Client$ParallelResults) > [junit] at > org.apache.hadoop.ipc.Client$ParallelCall.callComplete(Client.java:862) > [junit] at > org.apache.hadoop.ipc.Client$Call.setException(Client.java:185) > [junit] - locked <0xf59e2818> (a > org.apache.hadoop.ipc.Client$ParallelCall) > [junit] at > org.apache.hadoop.ipc.Client$Connection.cleanupCalls(Client.java:843) > [junit] at > org.apache.hadoop.ipc.Client$Connection.close(Client.java:832) > [junit] - locked <0xf59d8a90> (a > org.apache.hadoop.ipc.Client$Connection) > [junit] at > org.apache.hadoop.ipc.Client$Connection.run(Client.java:708) > [junit] "Thread-242": > [junit] at > org.apache.hadoop.ipc.Client$Connection.markClosed(Client.java:788) > [junit] - waiting to lock <0xf59d8a90> (a > org.apache.hadoop.ipc.Client$Connection) > [junit] at > org.apache.hadoop.ipc.Client$Connection.sendParam(Client.java:742) > [junit] at org.apache.hadoop.ipc.Client.call(Client.java:1109) > [junit] - locked <0xf599ef88> (a > org.apache.hadoop.ipc.Client$ParallelResults) > [junit] at > org.apache.hadoop.ipc.TestIPC$ParallelCaller.run(TestIPC.java:135) -- 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
[jira] [Updated] (HADOOP-7586) Hadoop daemon does not clean up pid file upon normal shutdown
[ https://issues.apache.org/jira/browse/HADOOP-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7586: Fix Version/s: (was: 0.22.0) 0.22.1 > Hadoop daemon does not clean up pid file upon normal shutdown > - > > Key: HADOOP-7586 > URL: https://issues.apache.org/jira/browse/HADOOP-7586 > Project: Hadoop Common > Issue Type: Improvement > Components: scripts >Affects Versions: 0.22.0, 0.23.0, 0.24.0 > Environment: Linux >Reporter: Joep Rottinghuis >Assignee: Joep Rottinghuis >Priority: Minor > Fix For: 0.22.1 > > > hadoop-daemon.sh script created pid files on when namenode, jobtrackers, etc. > deamons are started. > When the deamon is stopped in a regular manner through the stop script, it > should clean up the pid file to indicate normal controlled exit. > Presence of a pid without running corresponding process would then indicated > abnormal end of the process. -- 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
[jira] [Updated] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7861: Issue Type: Improvement (was: Bug) > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- 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
[jira] [Updated] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7861: Attachment: changes2html.patch Will apply to all three projects instead of creating 3 jiras, as all 3 files are identical. > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- 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
[jira] [Updated] (HADOOP-7391) Copy the interrface classification documentation of HADOOP-5073 into javadoc
[ https://issues.apache.org/jira/browse/HADOOP-7391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7391: Fix Version/s: (was: 0.22.0) > Copy the interrface classification documentation of HADOOP-5073 into javadoc > > > Key: HADOOP-7391 > URL: https://issues.apache.org/jira/browse/HADOOP-7391 > Project: Hadoop Common > Issue Type: Bug >Reporter: Sanjay Radia >Assignee: Sanjay Radia > Attachments: Hadoop Interface Taxonomy.html > > > The documentation for interface classification in Jira Hadoop-5073 was not > copied to the Javadoc > of the classification. -- 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
[jira] [Updated] (HADOOP-7358) Improve log levels when exceptions caught in RPC handler
[ https://issues.apache.org/jira/browse/HADOOP-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7358: Resolution: Fixed Assignee: Todd Lipcon Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) I just committed this to trunk and 0.22 branch. Thank you Todd and Uma. > Improve log levels when exceptions caught in RPC handler > > > Key: HADOOP-7358 > URL: https://issues.apache.org/jira/browse/HADOOP-7358 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc >Affects Versions: 0.22.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 0.22.0 > > Attachments: HADOOP-7358.trunk.patch, hadoop-7358.txt > > > When a server implementation throws an exception handling an RPC, the Handler > thread catches it and logs it before responding with the exception over the > IPC channel. This is currently done at INFO level. > I'd like to propose that, if the exception is an unchecked exception, it > should be logged at WARN level instead. This can help alert operators when > they might be hitting some kind of bug. -- 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
[jira] [Updated] (HADOOP-7786) Remove HDFS-specific configuration keys defined in FsConfig
[ https://issues.apache.org/jira/browse/HADOOP-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7786: Fix Version/s: 0.22.0 > Remove HDFS-specific configuration keys defined in FsConfig > --- > > Key: HADOOP-7786 > URL: https://issues.apache.org/jira/browse/HADOOP-7786 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 0.21.1 >Reporter: Eli Collins >Assignee: Eli Collins > Fix For: 0.22.0 > > Attachments: HDFS-1900.txt, hadoop-7786-1.patch, hadoop-7786-2.patch > > > HADOOP-4952 added a couple HDFS-specific configuration values to common (the > block size and the replication factor) that conflict with the HDFS values (eg > have the wrong defaults, wrong key name), are not used by common or hdfs and > should be removed. After removing these I noticed the rest of FsConfig is > only used once outside a test, and isn't tagged as a public API, I think we > can remove it entirely. -- 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
[jira] [Updated] (HADOOP-6913) Circular initialization between UserGroupInformation and KerberosName
[ https://issues.apache.org/jira/browse/HADOOP-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6913: Fix Version/s: 0.22.0 > Circular initialization between UserGroupInformation and KerberosName > - > > Key: HADOOP-6913 > URL: https://issues.apache.org/jira/browse/HADOOP-6913 > Project: Hadoop Common > Issue Type: Bug > Components: security >Reporter: Kan Zhang >Assignee: Kan Zhang > Fix For: 0.22.0 > > Attachments: c6913-01.patch > > > If the first call to UGI is UGI.setConfiguration(conf), it will try to > initialize UGI class. During this initialization, the code calls > KerberosName.setConfiguration(). KerberosName's static initializer will in > turn call UGI.isSecurityEnabled(). Since UGI hasn't been completely > initialized yet, isSecurityEnabled() will re-initialize UGI with a DEFAULT > conf. As a result, the original conf used in UGI.setConfiguration(conf) will > be overwritten by the DEFAULT conf. -- 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
[jira] [Updated] (HADOOP-6940) RawLocalFileSystem's markSupported method misnamed markSupport
[ https://issues.apache.org/jira/browse/HADOOP-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6940: Fix Version/s: 0.22.0 > RawLocalFileSystem's markSupported method misnamed markSupport > -- > > Key: HADOOP-6940 > URL: https://issues.apache.org/jira/browse/HADOOP-6940 > Project: Hadoop Common > Issue Type: Bug > Components: fs >Reporter: Tom White >Assignee: Tom White >Priority: Minor > Fix For: 0.22.0 > > Attachments: HADOOP-6940.patch > > > It should be named markSupported to override the method defined in > InputStream. Since it doesn't change the default no harm is done. -- 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
[jira] [Updated] (HADOOP-7390) VersionInfo not generated properly in git after unsplit
[ https://issues.apache.org/jira/browse/HADOOP-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7390: Fix Version/s: 0.22.0 > VersionInfo not generated properly in git after unsplit > --- > > Key: HADOOP-7390 > URL: https://issues.apache.org/jira/browse/HADOOP-7390 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 0.22.0 >Reporter: Thomas Graves >Assignee: Todd Lipcon >Priority: Minor > Fix For: 0.22.0 > > Attachments: hadoop-7390.txt > > > The version information generated during the build of common when running > from git has revision and branch Unknown. I believe this started after the > unsplit: > @HadoopVersionAnnotation(version="0.22.0-SNAPSHOT", revision="Unknown", > branch="Unknown", > user="tgraves", date="Tue Jun 14 13:39:10 UTC 2011", > url="file:///home/tgraves/git/hadoop-common/common", > srcChecksum="0f78ea668971fe51e7ebf4f97f84eed2") > The ./src/saveVersion.sh script which generates the package-info.java file > with the version info looks for the presence of .git directory and that is > now a level up instead of in the common directory. -- 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
[jira] [Updated] (HADOOP-6815) refreshSuperUserGroupsConfiguration should use server side configuration for the refresh
[ https://issues.apache.org/jira/browse/HADOOP-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6815: Fix Version/s: 0.22.0 > refreshSuperUserGroupsConfiguration should use server side configuration for > the refresh > > > Key: HADOOP-6815 > URL: https://issues.apache.org/jira/browse/HADOOP-6815 > Project: Hadoop Common > Issue Type: Bug >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > Fix For: 0.22.0 > > Attachments: HADOOP-6815-1.patch, HADOOP-6815-2.patch, > HADOOP-6815-3.patch, HADOOP-6815-5.patch, HADOOP-6815-YH20-1.patch, > HADOOP-6815.patch > > -- 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
[jira] [Updated] (HADOOP-6873) using delegation token over hftp for long running clients (part of hdfs 1296)
[ https://issues.apache.org/jira/browse/HADOOP-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6873: Fix Version/s: 0.22.0 > using delegation token over hftp for long running clients (part of hdfs 1296) > - > > Key: HADOOP-6873 > URL: https://issues.apache.org/jira/browse/HADOOP-6873 > Project: Hadoop Common > Issue Type: Bug >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > Fix For: 0.22.0 > > Attachments: HADOOP-6873-2.patch, HADOOP-6873.patch > > -- 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
[jira] [Updated] (HADOOP-6903) Make AbstractFileSystem's methods public to allow filter-Fs like implementions in a differnt package than fs
[ https://issues.apache.org/jira/browse/HADOOP-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6903: Fix Version/s: 0.22.0 > Make AbstractFileSystem's methods public to allow filter-Fs like > implementions in a differnt package than fs > > > Key: HADOOP-6903 > URL: https://issues.apache.org/jira/browse/HADOOP-6903 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Sanjay Radia >Assignee: Sanjay Radia > Fix For: 0.22.0 > > Attachments: Hadoop-6903-2.patch, Hadoop-6903-3.patch, > Hadoop-6903-4.patch, Hadoop-6903-5.patch, Hadoop-6903-7.patch, > Hadoop-6903.patch > > > Make AbstractFileSystem's methods public to allow filter-Fs like > implementions in a differnt package than fs -- 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
[jira] [Updated] (HADOOP-7577) TT does not start due to backwards compatibility wrt. EventCounter
[ https://issues.apache.org/jira/browse/HADOOP-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7577: Fix Version/s: 0.22.0 > TT does not start due to backwards compatibility wrt. EventCounter > -- > > Key: HADOOP-7577 > URL: https://issues.apache.org/jira/browse/HADOOP-7577 > Project: Hadoop Common > Issue Type: Bug > Components: metrics >Affects Versions: 0.22.0 >Reporter: Joep Rottinghuis >Assignee: Joep Rottinghuis >Priority: Minor > Fix For: 0.22.0 > > Attachments: HADOOP-7577.patch > > > Between metrics1 and mertrics2 EventCounter was moved from o.a.h.log to > o.a.h.metrics.jvm. > On 0.20-security a wrapper marked with @Deprecated was added back to > o.a.h.log for compatibility, the same wrapper exists on trunk, but no on 0.22. > Without it the TT will fail to start with a ClassNotFoundException. > Hive configuration also point to this class in the log4j.properties. -- 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
[jira] [Updated] (HADOOP-6778) add isRunning() method to AbstractDelegationTokenSecretManager (for HDFS-1044)
[ https://issues.apache.org/jira/browse/HADOOP-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6778: Fix Version/s: 0.22.0 > add isRunning() method to AbstractDelegationTokenSecretManager (for > HDFS-1044) > --- > > Key: HADOOP-6778 > URL: https://issues.apache.org/jira/browse/HADOOP-6778 > Project: Hadoop Common > Issue Type: Bug >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > Fix For: 0.22.0 > > Attachments: HADOOP-6778.patch > > -- 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
[jira] [Updated] (HADOOP-6911) doc update for DelegationTokenFetcher (part of HDFS-1036)
[ https://issues.apache.org/jira/browse/HADOOP-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6911: Fix Version/s: 0.22.0 > doc update for DelegationTokenFetcher (part of HDFS-1036) > - > > Key: HADOOP-6911 > URL: https://issues.apache.org/jira/browse/HADOOP-6911 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Boris Shkolnik >Priority: Minor > Fix For: 0.22.0 > > Attachments: HADOOP-6911-doc-1.patch, HADOOP-6911-doc.patch > > -- 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
[jira] [Updated] (HADOOP-6714) FsShell 'hadoop fs -text' does not support compression codecs
[ https://issues.apache.org/jira/browse/HADOOP-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6714: Fix Version/s: 0.22.0 > FsShell 'hadoop fs -text' does not support compression codecs > - > > Key: HADOOP-6714 > URL: https://issues.apache.org/jira/browse/HADOOP-6714 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Patrick Angeles >Assignee: Patrick Angeles > Fix For: 0.22.0 > > Attachments: HADOOP-6714.patch, hadoop-6714-20-1.patch > > > Currently, 'hadoop fs -text myfile' looks at the first few magic bytes of a > file to determine whether it is gzip compressed or a sequence file. This > means 'fs -text' cannot properly decode .deflate or .bz2 files (or other > codecs specified via configuration). > It should be fairly straightforward to add support for other codecs by > checking the file extension against the CompressionCodecFactory to retrieve > an appropriate Codec. -- 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
[jira] [Updated] (HADOOP-6805) add buildDTServiceName method to SecurityUtil (as part of MAPREDUCE-1718)
[ https://issues.apache.org/jira/browse/HADOOP-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6805: Fix Version/s: 0.22.0 > add buildDTServiceName method to SecurityUtil (as part of MAPREDUCE-1718) > - > > Key: HADOOP-6805 > URL: https://issues.apache.org/jira/browse/HADOOP-6805 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > Fix For: 0.22.0 > > Attachments: HADOOP-6805.patch > > -- 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
[jira] [Updated] (HADOOP-6781) security audit log shouldn't have exception in it.
[ https://issues.apache.org/jira/browse/HADOOP-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6781: Fix Version/s: 0.22.0 > security audit log shouldn't have exception in it. > -- > > Key: HADOOP-6781 > URL: https://issues.apache.org/jira/browse/HADOOP-6781 > Project: Hadoop Common > Issue Type: Bug >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > Fix For: 0.22.0 > > Attachments: HADOOP-6781-1.patch, HADOOP-6781-BP20.patch, > HADOOP-6781.patch > > > security audit log in Server.java also prints the exception information. It > shouldn't be there. -- 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
[jira] [Updated] (HADOOP-6791) Refresh for proxy superuser config (common part for HDFS-1096)
[ https://issues.apache.org/jira/browse/HADOOP-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6791: Fix Version/s: 0.22.0 > Refresh for proxy superuser config (common part for HDFS-1096) > --- > > Key: HADOOP-6791 > URL: https://issues.apache.org/jira/browse/HADOOP-6791 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > Fix For: 0.22.0 > > Attachments: HADOOP-6791.patch > > -- 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
[jira] [Updated] (HADOOP-6832) Provide a web server plugin that uses a static user for the web UI
[ https://issues.apache.org/jira/browse/HADOOP-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6832: Fix Version/s: 0.22.0 > Provide a web server plugin that uses a static user for the web UI > -- > > Key: HADOOP-6832 > URL: https://issues.apache.org/jira/browse/HADOOP-6832 > Project: Hadoop Common > Issue Type: New Feature > Components: security >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Fix For: 0.22.0 > > Attachments: h-6382.patch, h-6832.patch, h-6832.patch, h-6832.patch, > hadoop-6832.txt, static-web-user.patch > > > We need a simple plugin that uses a static user for clusters with security > that don't want to authenticate users on the web UI. -- 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
[jira] [Updated] (HADOOP-6970) SecurityAuth.audit should be generated under /build
[ https://issues.apache.org/jira/browse/HADOOP-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6970: Fix Version/s: 0.22.0 > SecurityAuth.audit should be generated under /build > --- > > Key: HADOOP-6970 > URL: https://issues.apache.org/jira/browse/HADOOP-6970 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 0.22.0, 0.23.0 >Reporter: Konstantin Shvachko >Assignee: Boris Shkolnik > Fix For: 0.22.0 > > Attachments: SecurityAudit-Trunk.patch > > > SecurityAuth.audit is generated under currently root project directory > whenever I run anything, and is not being cleaned up by the clean target. It > should be created under build directory instead. -- 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
[jira] [Updated] (HADOOP-7335) Force entropy to come from non-true random for tests
[
https://issues.apache.org/jira/browse/HADOOP-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HADOOP-7335:
Fix Version/s: 0.22.0
> Force entropy to come from non-true random for tests
>
>
> Key: HADOOP-7335
> URL: https://issues.apache.org/jira/browse/HADOOP-7335
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build, test
>Affects Versions: 0.22.0
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
>Priority: Minor
> Fix For: 0.22.0
>
> Attachments: hadoop-7335.txt
>
>
> Passing the system property {{-Djava.security.egd=file:///dev/urandom}}
> forces the JVM to seed its PRNG from non-true random (/dev/urandom) instead
> of the true random (/dev/random). This makes the tests run faster, since
> without it they often hang waiting for entropy while Jetty is initializing.
> We should turn this on for the test targets by default, so developers/hudson
> boxes don't have to make this change system-wide or use workarounds like
> rngtools.
--
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
[jira] [Updated] (HADOOP-6941) Support non-SUN JREs in UserGroupInformation
[ https://issues.apache.org/jira/browse/HADOOP-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-6941: Fix Version/s: (was: 0.22.0) > Support non-SUN JREs in UserGroupInformation > > > Key: HADOOP-6941 > URL: https://issues.apache.org/jira/browse/HADOOP-6941 > Project: Hadoop Common > Issue Type: Bug > Environment: SLES 11, Apache Harmony 6 and SLES 11, IBM Java 6 >Reporter: Stephen Watt >Assignee: Stephen Watt > Fix For: 0.21.1, 0.23.0 > > Attachments: HADOOP-6941.patch, hadoop-6941.patch > > > Attempting to format the namenode or attempting to start Hadoop using Apache > Harmony or the IBM Java JREs results in the following exception: > 10/09/07 16:35:05 ERROR namenode.NameNode: java.lang.NoClassDefFoundError: > com.sun.security.auth.UnixPrincipal > at > org.apache.hadoop.security.UserGroupInformation.(UserGroupInformation.java:223) > at java.lang.J9VMInternals.initializeImpl(Native Method) > at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.setConfigurationParameters(FSNamesystem.java:420) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:391) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:1240) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1348) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1368) > Caused by: java.lang.ClassNotFoundException: > com.sun.security.auth.UnixPrincipal > at java.net.URLClassLoader.findClass(URLClassLoader.java:421) > at java.lang.ClassLoader.loadClass(ClassLoader.java:652) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:346) > at java.lang.ClassLoader.loadClass(ClassLoader.java:618) > ... 8 more > This is a negative regression as previous versions of Hadoop worked with > these JREs -- 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
[jira] [Updated] (HADOOP-7176) Redesign FsShell
[ https://issues.apache.org/jira/browse/HADOOP-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7176: Fix Version/s: (was: 0.22.0) > Redesign FsShell > > > Key: HADOOP-7176 > URL: https://issues.apache.org/jira/browse/HADOOP-7176 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 0.22.0 >Reporter: Daryn Sharp >Assignee: Daryn Sharp > > The FsShell commands are very tightly coupled together which makes it > necessarily hard to write new commands. There is a lot of redundancy between > the commands, inconsistencies in handling of paths, handling of errors, and > correct return of exit codes. The FsShell commands should be subclasses of > the fs.shell.Command class which is already being used by the -count command, > and is used by other commands like dfsadmin. > This will serve as an umbrella bug to track the changes. -- 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
[jira] [Updated] (HADOOP-7697) Remove dependency on different version of slf4j in avro
[ https://issues.apache.org/jira/browse/HADOOP-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7697: Attachment: ivyXml-common.patch Also needs to be excluded from hadoop-common templates. > Remove dependency on different version of slf4j in avro > --- > > Key: HADOOP-7697 > URL: https://issues.apache.org/jira/browse/HADOOP-7697 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 0.22.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: ivyXml-common.patch, ivyXml-common.patch > > > Avro upgrade led to a mixture of slf4j versions. Hadoop uses slf4j 1.5.11, > and avro brings in 1.6.1 -- 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
[jira] [Updated] (HADOOP-7697) Remove dependency on different version of slf4j in avro
[ https://issues.apache.org/jira/browse/HADOOP-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7697: Attachment: ivyXml-common.patch > Remove dependency on different version of slf4j in avro > --- > > Key: HADOOP-7697 > URL: https://issues.apache.org/jira/browse/HADOOP-7697 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 0.22.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: ivyXml-common.patch > > > Avro upgrade led to a mixture of slf4j versions. Hadoop uses slf4j 1.5.11, > and avro brings in 1.6.1 -- 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
[jira] [Updated] (HADOOP-7646) Make hadoop-common use same version of avro as HBase
[ https://issues.apache.org/jira/browse/HADOOP-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7646: Attachment: HADOOP-7646-branch-22-shv.patch Removed white space change. > Make hadoop-common use same version of avro as HBase > > > Key: HADOOP-7646 > URL: https://issues.apache.org/jira/browse/HADOOP-7646 > Project: Hadoop Common > Issue Type: Bug > Components: io, ipc >Affects Versions: 0.22.0 >Reporter: Joep Rottinghuis >Assignee: Joep Rottinghuis > Fix For: 0.22.0 > > Attachments: HADOOP-7646-branch-22-shv.patch, > HADOOP-7646-branch-22-shv.patch, HADOOP-7646-branch-22.patch, > HADOOP-7646-branch-22.patch, HADOOP-7646-branch-22.patch, > HADOOP-7646-branch-22.patch > > > HBase depends on avro 1.5.3 whereas hadoop-common depends on 1.3.2. > When building HBase on top of hadoop, this should be consistent. -- 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
[jira] [Updated] (HADOOP-7646) Make hadoop-common use same version of avro as HBase
[ https://issues.apache.org/jira/browse/HADOOP-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7646: Attachment: HADOOP-7646-branch-22-shv.patch Here is a modification. The point is that BinaryEncoder needs to flush before written data will be available for the reader. Looks like a difference in semantics with the old avro. > Make hadoop-common use same version of avro as HBase > > > Key: HADOOP-7646 > URL: https://issues.apache.org/jira/browse/HADOOP-7646 > Project: Hadoop Common > Issue Type: Bug > Components: io, ipc >Affects Versions: 0.22.0 >Reporter: Joep Rottinghuis >Assignee: Joep Rottinghuis > Fix For: 0.22.0 > > Attachments: HADOOP-7646-branch-22-shv.patch, > HADOOP-7646-branch-22.patch, HADOOP-7646-branch-22.patch, > HADOOP-7646-branch-22.patch, HADOOP-7646-branch-22.patch > > > HBase depends on avro 1.5.3 whereas hadoop-common depends on 1.3.2. > When building HBase on top of hadoop, this should be consistent. -- 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
