[Discuss] Merge federation branch HDFS-1052 into trunk
A few weeks ago, I had sent an email about the progress of HDFS federation development in HDFS-1052 branch. I am happy to announce that all the tasks related to this feature development is complete and it is ready to be integrated into trunk. I have a merge patch attached to HDFS-1052 jira. All Hudson tests pass except for two test failures. We will fix these unit test failures in trunk, post merge. I plan on completing merge to trunk early next week. I would like to do this ASAP to avoid having to keep the patch up to date (which has been time consuming). This also avoids need for re-merging, due to SVN changes proposed by Nigel, scheduled late next week. Comments are welcome. Regards, Suresh
[jira] [Created] (HDFS-1860) when renewing/canceling DelegationToken over http we need to pass exception information back to the caller.
when renewing/canceling DelegationToken over http we need to pass exception information back to the caller. --- Key: HDFS-1860 URL: https://issues.apache.org/jira/browse/HDFS-1860 Project: Hadoop HDFS Issue Type: Bug Reporter: Boris Shkolnik Current implementation is not using XML for that, so we will pass it as a part of response message. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HDFS-1842) Cannot upgrade 0.20.203 to 0.21 with an editslog present
[ https://issues.apache.org/jira/browse/HDFS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-1842. --- Resolution: Fixed Release Note: I committed the patch. Konstantin, I wanted to commit this patch, as soon as possible. Please do review and let me know your feedback. I will open another jira to take care of the comments, if there are any. Hadoop Flags: [Reviewed] > Cannot upgrade 0.20.203 to 0.21 with an editslog present > > > Key: HDFS-1842 > URL: https://issues.apache.org/jira/browse/HDFS-1842 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Affects Versions: 0.20.203.0 >Reporter: Allen Wittenauer >Priority: Blocker > Attachments: HDFS-1842.rel203.patch, HDFS-1842.rel204.2.patch, > HDFS-1842.rel204.3.patch, HDFS-1842.rel204.patch > > > If a user installs 0.20.203 and then upgrades to 0.21 with an editslog > present, 0.21 will corrupt the file system due to opcode re-usage. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-1861) Rename dfs.datanode.max.xcievers and bump it's default value
Rename dfs.datanode.max.xcievers and bump it's default value Key: HDFS-1861 URL: https://issues.apache.org/jira/browse/HDFS-1861 Project: Hadoop HDFS Issue Type: Improvement Reporter: Eli Collins Assignee: Eli Collins Fix For: 0.23.0 Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice. Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
