[jira] [Commented] (HDFS-2395) webhdfs api's should return a root element in the json response
[ https://issues.apache.org/jira/browse/HDFS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120706#comment-13120706 ] Suresh Srinivas commented on HDFS-2395: --- +1 for both the patches. > webhdfs api's should return a root element in the json response > --- > > Key: HDFS-2395 > URL: https://issues.apache.org/jira/browse/HDFS-2395 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Tsz Wo (Nicholas), SZE >Priority: Critical > Attachments: h2395_20111003.patch, h2395_20111004.patch, > h2395_20111004_0.20s.patch, h2395_20111004b.patch, h2395_20111004c.patch, > h2395_20111004c_0.20s.patch, h2395_20111004d.patch, > h2395_20111004d_0.20s.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] (HDFS-2395) webhdfs api's should return a root element in the json response
[ https://issues.apache.org/jira/browse/HDFS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2395: - Attachment: h2395_20111004d.patch h2395_20111004d_0.20s.patch h2395_20111004d_0.20s.patch h2395_20111004d.patch Thanks Suresh for the review. The new patches incorporated all your comments. For the comments unrelated to this patch, I will change separately. > webhdfs api's should return a root element in the json response > --- > > Key: HDFS-2395 > URL: https://issues.apache.org/jira/browse/HDFS-2395 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Tsz Wo (Nicholas), SZE >Priority: Critical > Attachments: h2395_20111003.patch, h2395_20111004.patch, > h2395_20111004_0.20s.patch, h2395_20111004b.patch, h2395_20111004c.patch, > h2395_20111004c_0.20s.patch, h2395_20111004d.patch, > h2395_20111004d_0.20s.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] [Commented] (HDFS-2395) webhdfs api's should return a root element in the json response
[
https://issues.apache.org/jira/browse/HDFS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120691#comment-13120691
]
Suresh Srinivas commented on HDFS-2395:
---
# JsonUtil.java:
#* toJsonMap(ExtendedBlock...) javadoc says LocatedBlock.
#* minor: Instead of calling JsonUtil.method(), you could drop "JsonUtil." and
just call the method().
#* FileSystem.LOG.info XXX is needed?
#* minor: {{JsonUtil.toJsonString(Token.class.getSimpleName()}} could benefit
from having a variant JsonUtil.toJsonString(Class, map) which could call
getSimpleName() with in the method.
#* minor: cast is unnecessary {{array[i] = (DatanodeInfo)toDatanodeInfo((Map) objects[i]);}}
#* main method is no longer necessary
Unrelated to this patch:
# WebHdfsFileSystem#ugi hides HftpFileSystem#ugi
# NamenodeWebHdfsMethods
#* renewer not used in #generateDelegationToken
#* #put() does not use InputStream {{in}} and should not throw
URISyntaxException
#* #post() does not use InputStream {{in}} and should not throw
URISyntaxException
#* #get() should not throw URISyntaxException
Are these APIs going to be documented?
> webhdfs api's should return a root element in the json response
> ---
>
> Key: HDFS-2395
> URL: https://issues.apache.org/jira/browse/HDFS-2395
> Project: Hadoop HDFS
> Issue Type: Bug
>Affects Versions: 0.20.205.0
>Reporter: Arpit Gupta
>Assignee: Tsz Wo (Nicholas), SZE
>Priority: Critical
> Attachments: h2395_20111003.patch, h2395_20111004.patch,
> h2395_20111004_0.20s.patch, h2395_20111004b.patch, h2395_20111004c.patch,
> h2395_20111004c_0.20s.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] (HDFS-2395) webhdfs api's should return a root element in the json response
[ https://issues.apache.org/jira/browse/HDFS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2395: - Attachment: h2395_20111004c.patch h2395_20111004c_0.20s.patch h2395_20111004c_0.20s.patch h2395_20111004c.patch Cleaned up the patch for trunk and got the 0.20s patch. > webhdfs api's should return a root element in the json response > --- > > Key: HDFS-2395 > URL: https://issues.apache.org/jira/browse/HDFS-2395 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Tsz Wo (Nicholas), SZE >Priority: Critical > Attachments: h2395_20111003.patch, h2395_20111004.patch, > h2395_20111004_0.20s.patch, h2395_20111004b.patch, h2395_20111004c.patch, > h2395_20111004c_0.20s.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] (HDFS-2395) webhdfs api's should return a root element in the json response
[ https://issues.apache.org/jira/browse/HDFS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2395: - Attachment: h2395_20111004b.patch h2395_20111004b.patch: should not use JSON.toString(m) for the intermediate objects. > webhdfs api's should return a root element in the json response > --- > > Key: HDFS-2395 > URL: https://issues.apache.org/jira/browse/HDFS-2395 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Tsz Wo (Nicholas), SZE >Priority: Critical > Attachments: h2395_20111003.patch, h2395_20111004.patch, > h2395_20111004_0.20s.patch, h2395_20111004b.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] (HDFS-1762) Allow TestHDFSCLI to be run against a cluster
[ https://issues.apache.org/jira/browse/HDFS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HDFS-1762: - Component/s: test build > Allow TestHDFSCLI to be run against a cluster > - > > Key: HDFS-1762 > URL: https://issues.apache.org/jira/browse/HDFS-1762 > Project: Hadoop HDFS > Issue Type: Test > Components: build, test >Affects Versions: 0.22.0 >Reporter: Tom White >Assignee: Konstantin Boudnik > Attachments: HDFS-1762-20.patch, HDFS-1762.common.patch, > HDFS-1762.hdfs.patch, HDFS-1762.mapreduce.patch > > > Currently TestHDFSCLI starts mini clusters to run tests against. It would be > useful to be able to support running against arbitrary clusters for testing > purposes. -- 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] (HDFS-1762) Allow TestHDFSCLI to be run against a cluster
[ https://issues.apache.org/jira/browse/HDFS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HDFS-1762: - Attachment: HDFS-1762.mapreduce.patch HDFS-1762.hdfs.patch HDFS-1762.common.patch These are patches for all three subprojects for 0.22 branch. I will create separate tickets in a bit. They should be mostly good for 0.23 except the ant build part which needs to be re-worked for maven. > Allow TestHDFSCLI to be run against a cluster > - > > Key: HDFS-1762 > URL: https://issues.apache.org/jira/browse/HDFS-1762 > Project: Hadoop HDFS > Issue Type: Test >Affects Versions: 0.22.0 >Reporter: Tom White >Assignee: Konstantin Boudnik > Attachments: HDFS-1762-20.patch, HDFS-1762.common.patch, > HDFS-1762.hdfs.patch, HDFS-1762.mapreduce.patch > > > Currently TestHDFSCLI starts mini clusters to run tests against. It would be > useful to be able to support running against arbitrary clusters for testing > purposes. -- 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] [Commented] (HDFS-1762) Allow TestHDFSCLI to be run against a cluster
[ https://issues.apache.org/jira/browse/HDFS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120658#comment-13120658 ] Konstantin Boudnik commented on HDFS-1762: -- Patches above works for local mini-cluster setup without any problem. I will be validating this with a real cluster before committing them. > Allow TestHDFSCLI to be run against a cluster > - > > Key: HDFS-1762 > URL: https://issues.apache.org/jira/browse/HDFS-1762 > Project: Hadoop HDFS > Issue Type: Test >Affects Versions: 0.22.0 >Reporter: Tom White >Assignee: Konstantin Boudnik > Attachments: HDFS-1762-20.patch, HDFS-1762.common.patch, > HDFS-1762.hdfs.patch, HDFS-1762.mapreduce.patch > > > Currently TestHDFSCLI starts mini clusters to run tests against. It would be > useful to be able to support running against arbitrary clusters for testing > purposes. -- 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] [Commented] (HDFS-2385) Support delegation token renewal in webhdfs
[ https://issues.apache.org/jira/browse/HDFS-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120647#comment-13120647 ] Tsz Wo (Nicholas), SZE commented on HDFS-2385: -- I have committed h2385_20111004b_0.20s.patch to branch-0.20-security-205 and branch-0.20-security. > Support delegation token renewal in webhdfs > --- > > Key: HDFS-2385 > URL: https://issues.apache.org/jira/browse/HDFS-2385 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Fix For: 0.20.205.0, 0.20.206.0 > > Attachments: h2358_20111001_0.20s.patch, h2385_20111004_0.20s.patch, > h2385_20111004b_0.20s.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] [Commented] (HDFS-2181) Seperate HDFS wire protocol data types
[ https://issues.apache.org/jira/browse/HDFS-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120645#comment-13120645 ] Hadoop QA commented on HDFS-2181: - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12497736/separateDataType19.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1335//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1335//console This message is automatically generated. > Seperate HDFS wire protocol data types > -- > > Key: HDFS-2181 > URL: https://issues.apache.org/jira/browse/HDFS-2181 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Sanjay Radia >Assignee: Sanjay Radia > Attachments: separateDataType1.patch, separateDataType10.patch, > separateDataType11.patch, separateDataType12.patch, separateDataType13.patch, > separateDataType14.patch, separateDataType16.patch, separateDataType19.patch, > separateDataType2.patch, separateDataType6.patch, separateDataType7.patch, > separateDataType8.patch, separateDataType9.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] [Commented] (HDFS-2385) Support delegation token renewal in webhdfs
[ https://issues.apache.org/jira/browse/HDFS-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120633#comment-13120633 ] Jitendra Nath Pandey commented on HDFS-2385: +1. > Support delegation token renewal in webhdfs > --- > > Key: HDFS-2385 > URL: https://issues.apache.org/jira/browse/HDFS-2385 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Fix For: 0.20.205.0, 0.20.206.0 > > Attachments: h2358_20111001_0.20s.patch, h2385_20111004_0.20s.patch, > h2385_20111004b_0.20s.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] (HDFS-2385) Support delegation token renewal in webhdfs
[ https://issues.apache.org/jira/browse/HDFS-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2385: - Attachment: h2385_20111004b_0.20s.patch Reverted the 0.20s patch due to HDFS-2402. h2385_20111004b_0.20s.patch: The DelegationTokenSelector constructor should remain public. > Support delegation token renewal in webhdfs > --- > > Key: HDFS-2385 > URL: https://issues.apache.org/jira/browse/HDFS-2385 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Fix For: 0.20.205.0, 0.20.206.0 > > Attachments: h2358_20111001_0.20s.patch, h2385_20111004_0.20s.patch, > h2385_20111004b_0.20s.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] [Resolved] (HDFS-2402) namenode does not start with can not access a member of class exception
[ https://issues.apache.org/jira/browse/HDFS-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-2402. -- Resolution: Not A Problem This was caused by HDFS-2385. I reverted the patch. So it is not a problem anymore. > namenode does not start with can not access a member of class exception > --- > > Key: HDFS-2402 > URL: https://issues.apache.org/jira/browse/HDFS-2402 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Jitendra Nath Pandey >Priority: Blocker > -- 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] (HDFS-2181) Seperate HDFS wire protocol data types
[ https://issues.apache.org/jira/browse/HDFS-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HDFS-2181: --- Status: Patch Available (was: Open) > Seperate HDFS wire protocol data types > -- > > Key: HDFS-2181 > URL: https://issues.apache.org/jira/browse/HDFS-2181 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Sanjay Radia >Assignee: Sanjay Radia > Attachments: separateDataType1.patch, separateDataType10.patch, > separateDataType11.patch, separateDataType12.patch, separateDataType13.patch, > separateDataType14.patch, separateDataType16.patch, separateDataType19.patch, > separateDataType2.patch, separateDataType6.patch, separateDataType7.patch, > separateDataType8.patch, separateDataType9.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] (HDFS-2181) Seperate HDFS wire protocol data types
[ https://issues.apache.org/jira/browse/HDFS-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HDFS-2181: --- Status: Open (was: Patch Available) > Seperate HDFS wire protocol data types > -- > > Key: HDFS-2181 > URL: https://issues.apache.org/jira/browse/HDFS-2181 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Sanjay Radia >Assignee: Sanjay Radia > Attachments: separateDataType1.patch, separateDataType10.patch, > separateDataType11.patch, separateDataType12.patch, separateDataType13.patch, > separateDataType14.patch, separateDataType16.patch, separateDataType19.patch, > separateDataType2.patch, separateDataType6.patch, separateDataType7.patch, > separateDataType8.patch, separateDataType9.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] (HDFS-2181) Seperate HDFS wire protocol data types
[ https://issues.apache.org/jira/browse/HDFS-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HDFS-2181: --- Attachment: separateDataType19.patch * Addressed Todd's feedback. (R23 datatypes are xxxWritable) * Made the protocol names constants > Seperate HDFS wire protocol data types > -- > > Key: HDFS-2181 > URL: https://issues.apache.org/jira/browse/HDFS-2181 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Sanjay Radia >Assignee: Sanjay Radia > Attachments: separateDataType1.patch, separateDataType10.patch, > separateDataType11.patch, separateDataType12.patch, separateDataType13.patch, > separateDataType14.patch, separateDataType16.patch, separateDataType19.patch, > separateDataType2.patch, separateDataType6.patch, separateDataType7.patch, > separateDataType8.patch, separateDataType9.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] (HDFS-2402) namenode does not start with can not access a member of class exception
[ https://issues.apache.org/jira/browse/HDFS-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Gupta updated HDFS-2402: -- Affects Version/s: 0.20.205.0 > namenode does not start with can not access a member of class exception > --- > > Key: HDFS-2402 > URL: https://issues.apache.org/jira/browse/HDFS-2402 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Jitendra Nath Pandey >Priority: Blocker > -- 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] [Commented] (HDFS-2402) namenode does not start with can not access a member of class exception
[ https://issues.apache.org/jira/browse/HDFS-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120601#comment-13120601 ] Arpit Gupta commented on HDFS-2402: --- namenode log 2011-10-05 00:03:18,369 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: java.io.IOException: java.lang.IllegalAccessException: Class org.apache.hadoop.ipc.Client$Connection can not access a member of class org.apache.hadoop.hdfs.security.token.delegation.DelegationTokenSelector with modifiers "private" at org.apache.hadoop.ipc.Client$Connection.(Client.java:237) at org.apache.hadoop.ipc.Client.getConnection(Client.java:1192) at org.apache.hadoop.ipc.Client.call(Client.java:1046) at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:225) at $Proxy7.getProtocolVersion(Unknown Source) at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:396) at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:379) at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:118) at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:222) at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:187) at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:89) at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1328) at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:65) at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1346) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:244) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:122) at org.apache.hadoop.fs.Trash.(Trash.java:62) at org.apache.hadoop.hdfs.server.namenode.NameNode.startTrashEmptier(NameNode.java:314) at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:310) at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:493) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1264) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1273) > namenode does not start with can not access a member of class exception > --- > > Key: HDFS-2402 > URL: https://issues.apache.org/jira/browse/HDFS-2402 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Jitendra Nath Pandey >Priority: Blocker > -- 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] [Created] (HDFS-2402) namenode does not start with can not access a member of class exception
namenode does not start with can not access a member of class exception --- Key: HDFS-2402 URL: https://issues.apache.org/jira/browse/HDFS-2402 Project: Hadoop HDFS Issue Type: Bug Reporter: Arpit Gupta Assignee: Jitendra Nath Pandey Priority: Blocker -- 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] [Commented] (HDFS-2401) Running a set of methods in a Single Test Class
[ https://issues.apache.org/jira/browse/HDFS-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120555#comment-13120555 ] Jonathan Eagles commented on HDFS-2401: --- failed test TestListCorruptFileBlocks works on my box with latest checkout > Running a set of methods in a Single Test Class > --- > > Key: HDFS-2401 > URL: https://issues.apache.org/jira/browse/HDFS-2401 > Project: Hadoop HDFS > Issue Type: Improvement > Components: build >Affects Versions: 0.23.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: HDFS-2401.patch > > > Instead of running every test method in a class, limit to specific testing > methods as describe in the link below. > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > Upgrade to the latest version of maven-surefire-plugin that has this feature. -- 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] [Commented] (HDFS-2397) Undeprecate SecondaryNameNode in 0.22, 0.23
[ https://issues.apache.org/jira/browse/HDFS-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120549#comment-13120549 ] Aaron T. Myers commented on HDFS-2397: -- +1. I see little advantage to using the CN vs. the 2NN, except for the vastly superior name. > Undeprecate SecondaryNameNode in 0.22, 0.23 > --- > > Key: HDFS-2397 > URL: https://issues.apache.org/jira/browse/HDFS-2397 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Affects Versions: 0.22.0, 0.23.0 >Reporter: Todd Lipcon > > I would like to consider un-deprecating the SecondaryNameNode for 0.23, and > amending the documentation to indicate that it is still the most trust-worthy > way to run checkpoints, and while CN/BN may have some advantages, they're not > battle hardened as of yet. The test coverage for the 2NN is far superior to > the CheckpointNode or BackupNode, and people have a lot more production > experience. Indicating that it is deprecated before we have expanded test > coverage of the CN/BN won't send the right message to our users. (For > comparison, look at what a mess we got into by prematurely deprecating the > "old" MR API before the "new" API had feature parity and a few versions of > bug fixes). -- 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] [Commented] (HDFS-2401) Running a set of methods in a Single Test Class
[ https://issues.apache.org/jira/browse/HDFS-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120515#comment-13120515 ] Jonathan Eagles commented on HDFS-2401: --- No unit test changes need due to build system changes only. > Running a set of methods in a Single Test Class > --- > > Key: HDFS-2401 > URL: https://issues.apache.org/jira/browse/HDFS-2401 > Project: Hadoop HDFS > Issue Type: Improvement > Components: build >Affects Versions: 0.23.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: HDFS-2401.patch > > > Instead of running every test method in a class, limit to specific testing > methods as describe in the link below. > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > Upgrade to the latest version of maven-surefire-plugin that has this feature. -- 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] [Commented] (HDFS-2401) Running a set of methods in a Single Test Class
[ https://issues.apache.org/jira/browse/HDFS-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120514#comment-13120514 ] Hadoop QA commented on HDFS-2401: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12497684/HDFS-2401.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hdfs.server.namenode.TestListCorruptFileBlocks +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1334//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1334//console This message is automatically generated. > Running a set of methods in a Single Test Class > --- > > Key: HDFS-2401 > URL: https://issues.apache.org/jira/browse/HDFS-2401 > Project: Hadoop HDFS > Issue Type: Improvement > Components: build >Affects Versions: 0.23.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: HDFS-2401.patch > > > Instead of running every test method in a class, limit to specific testing > methods as describe in the link below. > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > Upgrade to the latest version of maven-surefire-plugin that has this feature. -- 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] [Commented] (HDFS-2395) webhdfs api's should return a root element in the json response
[ https://issues.apache.org/jira/browse/HDFS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120474#comment-13120474 ] Hadoop QA commented on HDFS-2395: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12497663/h2395_20111004.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1333//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1333//console This message is automatically generated. > webhdfs api's should return a root element in the json response > --- > > Key: HDFS-2395 > URL: https://issues.apache.org/jira/browse/HDFS-2395 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Tsz Wo (Nicholas), SZE >Priority: Critical > Attachments: h2395_20111003.patch, h2395_20111004.patch, > h2395_20111004_0.20s.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] (HDFS-2395) webhdfs api's should return a root element in the json response
[ https://issues.apache.org/jira/browse/HDFS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HDFS-2395: --- Priority: Critical (was: Major) Thanks for catching this flaw in our design before we ship our first release. Upgrading this to critical. > webhdfs api's should return a root element in the json response > --- > > Key: HDFS-2395 > URL: https://issues.apache.org/jira/browse/HDFS-2395 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Tsz Wo (Nicholas), SZE >Priority: Critical > Attachments: h2395_20111003.patch, h2395_20111004.patch, > h2395_20111004_0.20s.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] [Commented] (HDFS-1260) 0.20: Block lost when multiple DNs trying to recover it to different genstamps
[ https://issues.apache.org/jira/browse/HDFS-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120459#comment-13120459 ] Todd Lipcon commented on HDFS-1260: --- I don't believe so - I think the new append design in trunk prevents this issue. There is an existing open JIRA against trunk about forward-porting all append-related test cases to the new trunk implementation to be sure the new design doesn't suffer from the same issues. > 0.20: Block lost when multiple DNs trying to recover it to different genstamps > -- > > Key: HDFS-1260 > URL: https://issues.apache.org/jira/browse/HDFS-1260 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20-append >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Critical > Fix For: 0.20.205.0 > > Attachments: HDFS-1260-20S.3.patch, hdfs-1260.txt, hdfs-1260.txt, > simultaneous-recoveries.txt > > > Saw this issue on a cluster where some ops people were doing network changes > without shutting down DNs first. So, recovery ended up getting started at > multiple different DNs at the same time, and some race condition occurred > that caused a block to get permanently stuck in recovery mode. What seems to > have happened is the following: > - FSDataset.tryUpdateBlock called with old genstamp 7091, new genstamp 7094, > while the block in the volumeMap (and on filesystem) was genstamp 7093 > - we find the block file and meta file based on block ID only, without > comparing gen stamp > - we rename the meta file to the new genstamp _7094 > - in updateBlockMap, we do comparison in the volumeMap by oldblock *without* > wildcard GS, so it does *not* update volumeMap > - validateBlockMetaData now fails with "blk_7739687463244048122_7094 does not > exist in blocks map" > After this point, all future recovery attempts to that node fail in > getBlockMetaDataInfo, since it finds the _7094 gen stamp in getStoredBlock > (since the meta file got renamed above) and then fails since _7094 isn't in > volumeMap in validateBlockMetadata > Making a unit test for this is probably going to be difficult, but doable. -- 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] [Commented] (HDFS-2181) Seperate HDFS wire protocol data types
[ https://issues.apache.org/jira/browse/HDFS-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120428#comment-13120428 ] Sanjay Radia commented on HDFS-2181: Thanks for the feedback. * Prefix. The right thing to do is to add a suffix Writable - ie BlockWritable (just like BlockProto). As we add new types in future releases, the protocol version will NOT change (recall the rule - add new types and new methods). This makes sense because at some point we will remove writables from all other HDFS types. I can make that change. * Javadoc - It took a lot of time to put it. Given that it is done I prefer to leave it in since it will not be too bad to maintain. I did a similar thing for AbstractFileSystem and the main motivation was that we could hand this to a QA person to write compatibility tests. It is kind of convenient "cursor over" when one is reading code in Eclipse. * nits - will fix. * arg0 arg1 - I copied the code from old types ... will fix. * @Todd "... GET_STATS_CAPACITY_IDX .. follow on Jira" - Agree. > Seperate HDFS wire protocol data types > -- > > Key: HDFS-2181 > URL: https://issues.apache.org/jira/browse/HDFS-2181 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Sanjay Radia >Assignee: Sanjay Radia > Attachments: separateDataType1.patch, separateDataType10.patch, > separateDataType11.patch, separateDataType12.patch, separateDataType13.patch, > separateDataType14.patch, separateDataType16.patch, separateDataType2.patch, > separateDataType6.patch, separateDataType7.patch, separateDataType8.patch, > separateDataType9.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] (HDFS-2401) Running a set of methods in a Single Test Class
[ https://issues.apache.org/jira/browse/HDFS-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated HDFS-2401: -- Status: Patch Available (was: Open) > Running a set of methods in a Single Test Class > --- > > Key: HDFS-2401 > URL: https://issues.apache.org/jira/browse/HDFS-2401 > Project: Hadoop HDFS > Issue Type: Improvement > Components: build >Affects Versions: 0.23.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: HDFS-2401.patch > > > Instead of running every test method in a class, limit to specific testing > methods as describe in the link below. > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > Upgrade to the latest version of maven-surefire-plugin that has this feature. -- 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] [Commented] (HDFS-2401) Running a set of methods in a Single Test Class
[ https://issues.apache.org/jira/browse/HDFS-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120409#comment-13120409 ] Jonathan Eagles commented on HDFS-2401: --- Ran a complete test suite (common/hdfs/mapreduce on changes) and all tests are passing on a build and rebuild. > Running a set of methods in a Single Test Class > --- > > Key: HDFS-2401 > URL: https://issues.apache.org/jira/browse/HDFS-2401 > Project: Hadoop HDFS > Issue Type: Improvement > Components: build >Affects Versions: 0.23.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: HDFS-2401.patch > > > Instead of running every test method in a class, limit to specific testing > methods as describe in the link below. > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > Upgrade to the latest version of maven-surefire-plugin that has this feature. -- 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] [Commented] (HDFS-2401) Running a set of methods in a Single Test Class
[ https://issues.apache.org/jira/browse/HDFS-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120408#comment-13120408 ] Jonathan Eagles commented on HDFS-2401: --- recreated an empty test.build.data dir. Running tests (for example mvn -Dtest=TestShell test) from a clean build will fail due to assumption that test.build.data dir is a build system provided directory. > Running a set of methods in a Single Test Class > --- > > Key: HDFS-2401 > URL: https://issues.apache.org/jira/browse/HDFS-2401 > Project: Hadoop HDFS > Issue Type: Improvement > Components: build >Affects Versions: 0.23.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: HDFS-2401.patch > > > Instead of running every test method in a class, limit to specific testing > methods as describe in the link below. > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > Upgrade to the latest version of maven-surefire-plugin that has this feature. -- 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] (HDFS-2401) Running a set of methods in a Single Test Class
[ https://issues.apache.org/jira/browse/HDFS-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated HDFS-2401: -- Attachment: HDFS-2401.patch > Running a set of methods in a Single Test Class > --- > > Key: HDFS-2401 > URL: https://issues.apache.org/jira/browse/HDFS-2401 > Project: Hadoop HDFS > Issue Type: Improvement > Components: build >Affects Versions: 0.23.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: HDFS-2401.patch > > > Instead of running every test method in a class, limit to specific testing > methods as describe in the link below. > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > Upgrade to the latest version of maven-surefire-plugin that has this feature. -- 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] [Created] (HDFS-2401) Running a set of methods in a Single Test Class
Running a set of methods in a Single Test Class --- Key: HDFS-2401 URL: https://issues.apache.org/jira/browse/HDFS-2401 Project: Hadoop HDFS Issue Type: Improvement Components: build Affects Versions: 0.23.0 Reporter: Jonathan Eagles Assignee: Jonathan Eagles Instead of running every test method in a class, limit to specific testing methods as describe in the link below. http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html Upgrade to the latest version of maven-surefire-plugin that has this feature. -- 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] (HDFS-2385) Support delegation token renewal in webhdfs
[ https://issues.apache.org/jira/browse/HDFS-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2385: - Fix Version/s: 0.20.206.0 0.20.205.0 Hadoop Flags: Reviewed I have committed this to 0.20.205.0 and 0.20.206.0. The patch for trunk has to wait for MAPREDUCE-2764. > Support delegation token renewal in webhdfs > --- > > Key: HDFS-2385 > URL: https://issues.apache.org/jira/browse/HDFS-2385 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Fix For: 0.20.205.0, 0.20.206.0 > > Attachments: h2358_20111001_0.20s.patch, h2385_20111004_0.20s.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] [Commented] (HDFS-1260) 0.20: Block lost when multiple DNs trying to recover it to different genstamps
[ https://issues.apache.org/jira/browse/HDFS-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120351#comment-13120351 ] Matt Foley commented on HDFS-1260: -- Todd, do we need this in trunk also? > 0.20: Block lost when multiple DNs trying to recover it to different genstamps > -- > > Key: HDFS-1260 > URL: https://issues.apache.org/jira/browse/HDFS-1260 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20-append >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Critical > Fix For: 0.20.205.0 > > Attachments: HDFS-1260-20S.3.patch, hdfs-1260.txt, hdfs-1260.txt, > simultaneous-recoveries.txt > > > Saw this issue on a cluster where some ops people were doing network changes > without shutting down DNs first. So, recovery ended up getting started at > multiple different DNs at the same time, and some race condition occurred > that caused a block to get permanently stuck in recovery mode. What seems to > have happened is the following: > - FSDataset.tryUpdateBlock called with old genstamp 7091, new genstamp 7094, > while the block in the volumeMap (and on filesystem) was genstamp 7093 > - we find the block file and meta file based on block ID only, without > comparing gen stamp > - we rename the meta file to the new genstamp _7094 > - in updateBlockMap, we do comparison in the volumeMap by oldblock *without* > wildcard GS, so it does *not* update volumeMap > - validateBlockMetaData now fails with "blk_7739687463244048122_7094 does not > exist in blocks map" > After this point, all future recovery attempts to that node fail in > getBlockMetaDataInfo, since it finds the _7094 gen stamp in getStoredBlock > (since the meta file got renamed above) and then fails since _7094 isn't in > volumeMap in validateBlockMetadata > Making a unit test for this is probably going to be difficult, but doable. -- 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] [Commented] (HDFS-2188) HDFS-1580: Make FSEditLog create its journals from a list of URIs rather than NNStorage
[ https://issues.apache.org/jira/browse/HDFS-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120334#comment-13120334 ] Jitendra Nath Pandey commented on HDFS-2188: +1 for the patch. > HDFS-1580: Make FSEditLog create its journals from a list of URIs rather than > NNStorage > --- > > Key: HDFS-2188 > URL: https://issues.apache.org/jira/browse/HDFS-2188 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Ivan Kelly >Assignee: Ivan Kelly > Fix For: 0.23.0 > > Attachments: HDFS-2188.diff, HDFS-2188.diff, HDFS-2188.diff, > HDFS-2188.diff, HDFS-2188.diff > > > Currently, FSEditLog retrieves the list of Journals to create from NNStorage. > Obviously this is file specific. This JIRA aims to remove this restriction to > make it possible to create journals of custom types. -- 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] [Commented] (HDFS-2392) Dist with hftp is failing again
[ https://issues.apache.org/jira/browse/HDFS-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120336#comment-13120336 ] Matt Foley commented on HDFS-2392: -- Is this also needed in trunk, or can we resolve it? Thanks. > Dist with hftp is failing again > --- > > Key: HDFS-2392 > URL: https://issues.apache.org/jira/browse/HDFS-2392 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node >Affects Versions: 0.20.205.0 >Reporter: Rajit Saha >Assignee: Daryn Sharp >Priority: Critical > Fix For: 0.20.205.0 > > Attachments: HDFS-2392.patch > > > $ hadoop distcp hftp://:50070/user/hadoopqa/input1/part-0 > /user/hadoopqa/out3 > 11/09/30 18:57:59 INFO tools.DistCp: srcPaths=[hftp:// Hostname>:50070/user/hadoopqa/input1/part-0] > 11/09/30 18:57:59 INFO tools.DistCp: destPath=/user/hadoopqa/out3 > 11/09/30 18:58:00 INFO security.TokenCache: Got dt for > hftp://:50070/user/hadoopqa/input1/part-0;uri= IP>:50470;t.service=:50470 > 11/09/30 18:58:00 INFO hdfs.DFSClient: Created HDFS_DELEGATION_TOKEN token 24 > for hadoopqa on :8020 > 11/09/30 18:58:00 INFO security.TokenCache: Got dt for > /user/hadoopqa/out3;uri=:8020;t.service=:8020 > 11/09/30 18:58:00 INFO tools.DistCp: /user/hadoopqa/out3 does not exist. > 11/09/30 18:58:00 INFO tools.DistCp: sourcePathsCount=1 > 11/09/30 18:58:00 INFO tools.DistCp: filesToCopyCount=1 > 11/09/30 18:58:00 INFO tools.DistCp: bytesToCopyCount=1.0g > 11/09/30 18:58:01 INFO mapred.JobClient: Running job: job_201109300819_0007 > 11/09/30 18:58:02 INFO mapred.JobClient: map 0% reduce 0% > 11/09/30 18:58:25 INFO mapred.JobClient: Task Id : > attempt_201109300819_0007_m_00_0, Status : FAILED > java.io.IOException: Copied: 0 Skipped: 0 Failed: 1 > at > org.apache.hadoop.tools.DistCp$CopyFilesMapper.close(DistCp.java:582) > at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:57) > at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:436) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:372) > at org.apache.hadoop.mapred.Child$4.run(Child.java:255) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:396) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1059) > at org.apache.hadoop.mapred.Child.main(Child.java:249) > 11/09/30 18:58:41 INFO mapred.JobClient: Task Id : > attempt_201109300819_0007_m_00_1, Status : FAILED > java.io.IOException: Copied: 0 Skipped: 0 Failed: 1 > at > org.apache.hadoop.tools.DistCp$CopyFilesMapper.close(DistCp.java:582) > at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:57) > at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:436) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:372) > at org.apache.hadoop.mapred.Child$4.run(Child.java:255) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:396) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1059) > at org.apache.hadoop.mapred.Child.main(Child.java:249) > 11/09/30 18:58:56 INFO mapred.JobClient: Task Id : > attempt_201109300819_0007_m_00_2, Status : FAILED > java.io.IOException: Copied: 0 Skipped: 0 Failed: 1 > at > org.apache.hadoop.tools.DistCp$CopyFilesMapper.close(DistCp.java:582) > at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:57) > at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:436) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:372) > at org.apache.hadoop.mapred.Child$4.run(Child.java:255) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:396) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1059) > at org.apache.hadoop.mapred.Child.main(Child.java:249) > 11/09/30 18:59:14 INFO mapred.JobClient: Job complete: job_201109300819_0007 > 11/09/30 18:59:14 INFO mapred.JobClient: Counters: 6 > 11/09/30 18:59:14 INFO mapred.JobClient: Job Counters > 11/09/30 18:59:14 INFO mapred.JobClient: SLOTS_MILLIS_MAPS=62380 > 11/09/30 18:59:14 INFO mapred.JobClient: Total time spent by all reduces > waiting after reserving slots (ms)=0 > 11/09/30 18:59:14 INFO mapred.JobClient: Total time spent by all maps > waiting after reserving slots (ms)=0 > 11/09/30 18:59:14 INFO mapred.JobClient: Launched map tasks=4 > 11/09/30 18:59:14 INFO mapred.JobClient: SLOTS_MILLIS_REDUCES=0 > 11/09/30 18:59:14 INFO mapred.JobClient: Failed m
[jira] [Commented] (HDFS-2181) Seperate HDFS wire protocol data types
[
https://issues.apache.org/jira/browse/HDFS-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120328#comment-13120328
]
Todd Lipcon commented on HDFS-2181:
---
Thanks for the thorough explanation. The general architecture makes sense. It
will be a bit of a pain to maintain, I think, but the benefits are probably
worth it.
A few general comments:
- Can we prefix all of the classes in protocolR23Compatible with the string
"R23"? So we have "R23Block" as the wire type and "Block" as the internal type?
Or "R23WBlock" to stand for R23 Writable Block, perhaps? My thinking is that it
will make the translator code easier to read because we don't need to fully
qualify all of the wire types with the really long package name. It may also
help in debugging since the short class name will differ. This is also helpful
when developers use autocomplete in the IDE - we don't want to accidentally
import the wire types into internal code.
- Do we really need to duplicate the javadoc "The specification of this method
matches that of ..." for every method in the R23 protocols? Just seems like a
lot of boilerplate that will cause javadoc warnings later if we add arguments
to existing methods in the non-wire protocol interface.
A few nits:
- Need an extra ". " in this concatenation:
{code}
+throw new IOException("Namenode Serverside implements "
++ ClientNamenodeProtocol.class
++ "The following requested protocol is unknown: " + protocol);
{code}
- There are a few spots where methods have arguments called {{arg0}}, {{arg1}},
etc.
- The constants GET_STATS_CAPACITY_IDX, etc, should probably be part of the
generic protocol, not the R23 protocol, since the FSNamesystem method itself
returns the array of longs. Perhaps we can just file a follow-up JIRA to
replace this with some kind of FileSystemStats class instead of the somewhat
ugly array?
> Seperate HDFS wire protocol data types
> --
>
> Key: HDFS-2181
> URL: https://issues.apache.org/jira/browse/HDFS-2181
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Sanjay Radia
>Assignee: Sanjay Radia
> Attachments: separateDataType1.patch, separateDataType10.patch,
> separateDataType11.patch, separateDataType12.patch, separateDataType13.patch,
> separateDataType14.patch, separateDataType16.patch, separateDataType2.patch,
> separateDataType6.patch, separateDataType7.patch, separateDataType8.patch,
> separateDataType9.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] [Commented] (HDFS-2385) Support delegation token renewal in webhdfs
[ https://issues.apache.org/jira/browse/HDFS-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120319#comment-13120319 ] Jitendra Nath Pandey commented on HDFS-2385: +1 for the patch. > Support delegation token renewal in webhdfs > --- > > Key: HDFS-2385 > URL: https://issues.apache.org/jira/browse/HDFS-2385 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2358_20111001_0.20s.patch, h2385_20111004_0.20s.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] [Commented] (HDFS-2392) Dist with hftp is failing again
[ https://issues.apache.org/jira/browse/HDFS-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120313#comment-13120313 ] Jitendra Nath Pandey commented on HDFS-2392: Thanks to Daryn for the patch. > Dist with hftp is failing again > --- > > Key: HDFS-2392 > URL: https://issues.apache.org/jira/browse/HDFS-2392 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node >Affects Versions: 0.20.205.0 >Reporter: Rajit Saha >Assignee: Daryn Sharp >Priority: Critical > Fix For: 0.20.205.0 > > Attachments: HDFS-2392.patch > > > $ hadoop distcp hftp://:50070/user/hadoopqa/input1/part-0 > /user/hadoopqa/out3 > 11/09/30 18:57:59 INFO tools.DistCp: srcPaths=[hftp:// Hostname>:50070/user/hadoopqa/input1/part-0] > 11/09/30 18:57:59 INFO tools.DistCp: destPath=/user/hadoopqa/out3 > 11/09/30 18:58:00 INFO security.TokenCache: Got dt for > hftp://:50070/user/hadoopqa/input1/part-0;uri= IP>:50470;t.service=:50470 > 11/09/30 18:58:00 INFO hdfs.DFSClient: Created HDFS_DELEGATION_TOKEN token 24 > for hadoopqa on :8020 > 11/09/30 18:58:00 INFO security.TokenCache: Got dt for > /user/hadoopqa/out3;uri=:8020;t.service=:8020 > 11/09/30 18:58:00 INFO tools.DistCp: /user/hadoopqa/out3 does not exist. > 11/09/30 18:58:00 INFO tools.DistCp: sourcePathsCount=1 > 11/09/30 18:58:00 INFO tools.DistCp: filesToCopyCount=1 > 11/09/30 18:58:00 INFO tools.DistCp: bytesToCopyCount=1.0g > 11/09/30 18:58:01 INFO mapred.JobClient: Running job: job_201109300819_0007 > 11/09/30 18:58:02 INFO mapred.JobClient: map 0% reduce 0% > 11/09/30 18:58:25 INFO mapred.JobClient: Task Id : > attempt_201109300819_0007_m_00_0, Status : FAILED > java.io.IOException: Copied: 0 Skipped: 0 Failed: 1 > at > org.apache.hadoop.tools.DistCp$CopyFilesMapper.close(DistCp.java:582) > at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:57) > at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:436) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:372) > at org.apache.hadoop.mapred.Child$4.run(Child.java:255) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:396) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1059) > at org.apache.hadoop.mapred.Child.main(Child.java:249) > 11/09/30 18:58:41 INFO mapred.JobClient: Task Id : > attempt_201109300819_0007_m_00_1, Status : FAILED > java.io.IOException: Copied: 0 Skipped: 0 Failed: 1 > at > org.apache.hadoop.tools.DistCp$CopyFilesMapper.close(DistCp.java:582) > at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:57) > at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:436) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:372) > at org.apache.hadoop.mapred.Child$4.run(Child.java:255) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:396) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1059) > at org.apache.hadoop.mapred.Child.main(Child.java:249) > 11/09/30 18:58:56 INFO mapred.JobClient: Task Id : > attempt_201109300819_0007_m_00_2, Status : FAILED > java.io.IOException: Copied: 0 Skipped: 0 Failed: 1 > at > org.apache.hadoop.tools.DistCp$CopyFilesMapper.close(DistCp.java:582) > at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:57) > at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:436) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:372) > at org.apache.hadoop.mapred.Child$4.run(Child.java:255) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:396) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1059) > at org.apache.hadoop.mapred.Child.main(Child.java:249) > 11/09/30 18:59:14 INFO mapred.JobClient: Job complete: job_201109300819_0007 > 11/09/30 18:59:14 INFO mapred.JobClient: Counters: 6 > 11/09/30 18:59:14 INFO mapred.JobClient: Job Counters > 11/09/30 18:59:14 INFO mapred.JobClient: SLOTS_MILLIS_MAPS=62380 > 11/09/30 18:59:14 INFO mapred.JobClient: Total time spent by all reduces > waiting after reserving slots (ms)=0 > 11/09/30 18:59:14 INFO mapred.JobClient: Total time spent by all maps > waiting after reserving slots (ms)=0 > 11/09/30 18:59:14 INFO mapred.JobClient: Launched map tasks=4 > 11/09/30 18:59:14 INFO mapred.JobClient: SLOTS_MILLIS_REDUCES=0 > 11/09/30 18:59:14 INFO mapred.JobClient: Failed map tasks=1
[jira] [Updated] (HDFS-2395) webhdfs api's should return a root element in the json response
[ https://issues.apache.org/jira/browse/HDFS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2395: - Attachment: h2395_20111004.patch h2395_20111004_0.20s.patch h2395_20111004_0.20s.patch h2395_20111004.patch Slightly changed the patch for trunk and added a patch for 0.20s. > webhdfs api's should return a root element in the json response > --- > > Key: HDFS-2395 > URL: https://issues.apache.org/jira/browse/HDFS-2395 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2395_20111003.patch, h2395_20111004.patch, > h2395_20111004_0.20s.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] (HDFS-2385) Support delegation token renewal in webhdfs
[ https://issues.apache.org/jira/browse/HDFS-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2385: - Attachment: h2385_20111004_0.20s.patch Thanks Jitendra for the review. I made all the change and sync the patch with trunk. h2385_20111004_0.20s.patch > Support delegation token renewal in webhdfs > --- > > Key: HDFS-2385 > URL: https://issues.apache.org/jira/browse/HDFS-2385 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2358_20111001_0.20s.patch, h2385_20111004_0.20s.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] [Commented] (HDFS-1073) Simpler model for Namenode's fs Image and edit Logs
[ https://issues.apache.org/jira/browse/HDFS-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120123#comment-13120123 ] Hudson commented on HDFS-1073: -- Integrated in Hadoop-Mapreduce-trunk #850 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/850/]) Fix CHANGES.txt to include complete subtask list for HDFS-1073. Somehow in the merge, some subtasks were lost from CHANGES.txt. I spot-checked these patches to make sure they were in fact merged, and it was only CHANGES.txt that was missing them. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1178610 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > Simpler model for Namenode's fs Image and edit Logs > > > Key: HDFS-1073 > URL: https://issues.apache.org/jira/browse/HDFS-1073 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 0.23.0 >Reporter: Sanjay Radia >Assignee: Todd Lipcon > Fix For: 0.23.0 > > Attachments: hdfs-1073-editloading-algos.txt, hdfs-1073-merge.patch, > hdfs-1073-merge.patch, hdfs-1073-merge.patch, hdfs-1073.txt, hdfs1073.pdf, > hdfs1073.pdf, hdfs1073.pdf, hdfs1073.tex > > > The naming and handling of NN's fsImage and edit logs can be significantly > improved resulting simpler and more robust 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] [Commented] (HDFS-1073) Simpler model for Namenode's fs Image and edit Logs
[ https://issues.apache.org/jira/browse/HDFS-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120109#comment-13120109 ] Hudson commented on HDFS-1073: -- Integrated in Hadoop-Hdfs-0.23-Build #29 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/29/]) Fix CHANGES.txt to include complete subtask list for HDFS-1073. Somehow in the merge, some subtasks were lost from CHANGES.txt. I spot-checked these patches to make sure they were in fact merged, and it was only CHANGES.txt that was missing them. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1178611 Files : * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > Simpler model for Namenode's fs Image and edit Logs > > > Key: HDFS-1073 > URL: https://issues.apache.org/jira/browse/HDFS-1073 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 0.23.0 >Reporter: Sanjay Radia >Assignee: Todd Lipcon > Fix For: 0.23.0 > > Attachments: hdfs-1073-editloading-algos.txt, hdfs-1073-merge.patch, > hdfs-1073-merge.patch, hdfs-1073-merge.patch, hdfs-1073.txt, hdfs1073.pdf, > hdfs1073.pdf, hdfs1073.pdf, hdfs1073.tex > > > The naming and handling of NN's fsImage and edit logs can be significantly > improved resulting simpler and more robust 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] [Commented] (HDFS-1073) Simpler model for Namenode's fs Image and edit Logs
[ https://issues.apache.org/jira/browse/HDFS-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120089#comment-13120089 ] Hudson commented on HDFS-1073: -- Integrated in Hadoop-Hdfs-trunk #820 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/820/]) Fix CHANGES.txt to include complete subtask list for HDFS-1073. Somehow in the merge, some subtasks were lost from CHANGES.txt. I spot-checked these patches to make sure they were in fact merged, and it was only CHANGES.txt that was missing them. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1178610 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > Simpler model for Namenode's fs Image and edit Logs > > > Key: HDFS-1073 > URL: https://issues.apache.org/jira/browse/HDFS-1073 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 0.23.0 >Reporter: Sanjay Radia >Assignee: Todd Lipcon > Fix For: 0.23.0 > > Attachments: hdfs-1073-editloading-algos.txt, hdfs-1073-merge.patch, > hdfs-1073-merge.patch, hdfs-1073-merge.patch, hdfs-1073.txt, hdfs1073.pdf, > hdfs1073.pdf, hdfs1073.pdf, hdfs1073.tex > > > The naming and handling of NN's fsImage and edit logs can be significantly > improved resulting simpler and more robust 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] [Commented] (HDFS-1073) Simpler model for Namenode's fs Image and edit Logs
[ https://issues.apache.org/jira/browse/HDFS-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120066#comment-13120066 ] Hudson commented on HDFS-1073: -- Integrated in Hadoop-Mapreduce-0.23-Build #36 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/36/]) Fix CHANGES.txt to include complete subtask list for HDFS-1073. Somehow in the merge, some subtasks were lost from CHANGES.txt. I spot-checked these patches to make sure they were in fact merged, and it was only CHANGES.txt that was missing them. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1178611 Files : * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > Simpler model for Namenode's fs Image and edit Logs > > > Key: HDFS-1073 > URL: https://issues.apache.org/jira/browse/HDFS-1073 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 0.23.0 >Reporter: Sanjay Radia >Assignee: Todd Lipcon > Fix For: 0.23.0 > > Attachments: hdfs-1073-editloading-algos.txt, hdfs-1073-merge.patch, > hdfs-1073-merge.patch, hdfs-1073-merge.patch, hdfs-1073.txt, hdfs1073.pdf, > hdfs1073.pdf, hdfs1073.pdf, hdfs1073.tex > > > The naming and handling of NN's fsImage and edit logs can be significantly > improved resulting simpler and more robust 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] [Commented] (HDFS-2181) Seperate HDFS wire protocol data types
[ https://issues.apache.org/jira/browse/HDFS-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119965#comment-13119965 ] Hadoop QA commented on HDFS-2181: - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12497592/separateDataType16.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1332//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1332//console This message is automatically generated. > Seperate HDFS wire protocol data types > -- > > Key: HDFS-2181 > URL: https://issues.apache.org/jira/browse/HDFS-2181 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Sanjay Radia >Assignee: Sanjay Radia > Attachments: separateDataType1.patch, separateDataType10.patch, > separateDataType11.patch, separateDataType12.patch, separateDataType13.patch, > separateDataType14.patch, separateDataType16.patch, separateDataType2.patch, > separateDataType6.patch, separateDataType7.patch, separateDataType8.patch, > separateDataType9.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] [Commented] (HDFS-2395) webhdfs api's should return a root element in the json response
[ https://issues.apache.org/jira/browse/HDFS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119948#comment-13119948 ] Hadoop QA commented on HDFS-2395: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12497590/h2395_20111003.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1331//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1331//console This message is automatically generated. > webhdfs api's should return a root element in the json response > --- > > Key: HDFS-2395 > URL: https://issues.apache.org/jira/browse/HDFS-2395 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.20.205.0 >Reporter: Arpit Gupta >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2395_20111003.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] [Commented] (HDFS-2385) Support delegation token renewal in webhdfs
[ https://issues.apache.org/jira/browse/HDFS-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119946#comment-13119946 ] Jitendra Nath Pandey commented on HDFS-2385: It may be possible to remove the getDelegationToken method from the Renewable interface, because it is used only in toString. This method is a bit confusing because the FileSystem also has a getDelegationToken which actually gets a token. Minor: setDelegationToken is changed to setDelegationTokens although it still takes only one token. > Support delegation token renewal in webhdfs > --- > > Key: HDFS-2385 > URL: https://issues.apache.org/jira/browse/HDFS-2385 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2358_20111001_0.20s.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
