[jira] [Commented] (HDFS-1776) Bug in Concat code
[ https://issues.apache.org/jira/browse/HDFS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070088#comment-13070088 ] Hudson commented on HDFS-1776: -- Integrated in Hadoop-Hdfs-trunk-Commit #803 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/803/]) HDFS-1776 Bug in Bug in Concat code. Contributed by Bharath Mundlapudi molkov : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1150247 Files : * /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/INodeFile.java * /hadoop/common/trunk/hdfs/CHANGES.txt * /hadoop/common/trunk/hdfs/src/test/unit/org/apache/hadoop/hdfs/server/namenode/TestINodeFile.java > Bug in Concat code > -- > > Key: HDFS-1776 > URL: https://issues.apache.org/jira/browse/HDFS-1776 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.23.0 >Reporter: Dmytro Molkov >Assignee: Bharath Mundlapudi > Fix For: 0.23.0 > > Attachments: HDFS-1776-1.patch > > > There is a bug in the concat code. Specifically: in INodeFile.appendBlocks() > we need to first reassign the blocks list and then go through it and update > the INode pointer. Otherwise we are not updating the inode pointer on all of > the new blocks in the file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1776) Bug in Concat code
[ https://issues.apache.org/jira/browse/HDFS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070086#comment-13070086 ] Dmytro Molkov commented on HDFS-1776: - I just committed this. Thanks Bharath > Bug in Concat code > -- > > Key: HDFS-1776 > URL: https://issues.apache.org/jira/browse/HDFS-1776 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.23.0 >Reporter: Dmytro Molkov >Assignee: Bharath Mundlapudi > Fix For: 0.23.0 > > Attachments: HDFS-1776-1.patch > > > There is a bug in the concat code. Specifically: in INodeFile.appendBlocks() > we need to first reassign the blocks list and then go through it and update > the INode pointer. Otherwise we are not updating the inode pointer on all of > the new blocks in the file. -- This message is automatically generated by JIRA. 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=13070077#comment-13070077 ] Todd Lipcon commented on HDFS-1073: --- Thanks for the comments. I did another sweep for unused imports and moved rollForwardByApplyingLogs like you suggested. I committed these changes to the branch. > 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.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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2171) Changes to balancer bandwidth should not require datanode restart.
[ https://issues.apache.org/jira/browse/HDFS-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070042#comment-13070042 ] Eric Payne commented on HDFS-2171: -- In my tests, the dfsadmin solution (option 3) seems to work well. After thinking about it, I like the dfsadmin solution best because the balancer utility can keep running while the bandwidth is adjusted. I'll create a unit test and post a patch Monday. -Eric > Changes to balancer bandwidth should not require datanode restart. > -- > > Key: HDFS-2171 > URL: https://issues.apache.org/jira/browse/HDFS-2171 > Project: Hadoop HDFS > Issue Type: Bug > Components: balancer, data-node >Affects Versions: 0.20.205.0 >Reporter: Eric Payne >Assignee: Eric Payne > Fix For: 0.20.205.0 > > > Currently in order to change the value of the balancer bandwidth > (dfs.datanode.balance.bandwidthPerSec), the datanode daemon must be restarted. > The optimal value of the bandwidthPerSec parameter is not always (almost > never) known at the time of cluster startup, but only once a new node is > placed in the cluster and balancing is begun. If the balancing is taking too > long (bandwidthPerSec is too low) or the balancing is taking up too much > bandwidth (bandwidthPerSec is too high), the cluster must go into a > "maintenance window" where it is unusable while all of the datanodes are > bounced. In large clusters of thousands of nodes, this can be a real > maintenance problem because these "mainenance windows" can take a long time > and there may have to be several of them while the bandwidthPerSec is > experimented with and tuned. > A possible solution to this problem would be to add a -bandwidth parameter to > the balancer tool. If bandwidth is supplied, pass the value to the datanodes > via the OP_REPLACE_BLOCK and OP_COPY_BLOCK DataTransferProtocol requests. > This would make it necessary, however, to change the DataTransferProtocol > version. -- This message is automatically generated by JIRA. 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=13070021#comment-13070021 ] Konstantin Shvachko commented on HDFS-1073: --- Did a quick sweep over warnings: # Remove unused imports: CheckpointSignature, EditLogFileOutputStream, FSEditLogLoader, TransferFsImage, NamenodeProtocol, NamenodeRegistration, NamespaceInfo, EditsLoaderCurrent, ImageLoaderCurrent. # Unused code: EditLogBackupInputStream.ByteBufferInputStream.getData() # Move SecondaryNameNode.rollForwardByApplyingLogs() into Checkpointer to avoid deprecation warning and to ease removal of SNN in the future. Looking further. > 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.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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2191) Move datanodeMap from FSNamesystem to DatanodeManager
[ https://issues.apache.org/jira/browse/HDFS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069977#comment-13069977 ] Hadoop QA commented on HDFS-2191: - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12487587/h2191_20110723b.patch against trunk revision 1150067. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 18 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 core unit tests. +1 contrib tests. The patch passed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1005//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1005//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1005//console This message is automatically generated. > Move datanodeMap from FSNamesystem to DatanodeManager > - > > Key: HDFS-2191 > URL: https://issues.apache.org/jira/browse/HDFS-2191 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2191_20110723.patch, h2191_20110723b.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2191) Move datanodeMap from FSNamesystem to DatanodeManager
[ https://issues.apache.org/jira/browse/HDFS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2191: - Attachment: h2191_20110723b.patch h2191_20110723b.patch: fixed the javadoc warnings. > Move datanodeMap from FSNamesystem to DatanodeManager > - > > Key: HDFS-2191 > URL: https://issues.apache.org/jira/browse/HDFS-2191 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2191_20110723.patch, h2191_20110723b.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1739) When DataNode throws DiskOutOfSpaceException, it will be helpfull to the user if we log the available volume size and configured block size.
[ https://issues.apache.org/jira/browse/HDFS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069948#comment-13069948 ] Hudson commented on HDFS-1739: -- Integrated in Hadoop-Hdfs-trunk #733 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/733/]) HDFS-1739. Add available volume size to the error message when datanode throws DiskOutOfSpaceException. Contributed by Uma Maheswara Rao G szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1150067 Files : * /hadoop/common/trunk/hdfs/CHANGES.txt * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/datanode/TestRoundRobinVolumesPolicy.java * /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/datanode/RoundRobinVolumesPolicy.java > When DataNode throws DiskOutOfSpaceException, it will be helpfull to the user > if we log the available volume size and configured block size. > > > Key: HDFS-1739 > URL: https://issues.apache.org/jira/browse/HDFS-1739 > Project: Hadoop HDFS > Issue Type: Improvement > Components: data-node >Affects Versions: 0.23.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G >Priority: Minor > Fix For: 0.23.0 > > Attachments: HDFS-1739.1.patch, HDFS-1739.2.patch, HDFS-1739.3.patch, > HDFS-1739.4.patch, HDFS-1739.5.patch, HDFS-1739.patch > > > DataNode will throw DiskOutOfSpaceException for new blcok write if available > volume size is less than configured blcok size. > So, it will be helpfull to the user if we log this details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2116) Cleanup TestStreamFile and TestByteRangeInputStream
[ https://issues.apache.org/jira/browse/HDFS-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069950#comment-13069950 ] Hudson commented on HDFS-2116: -- Integrated in Hadoop-Hdfs-trunk #733 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/733/]) HDFS-2116. Use Mokito in TestStreamFile and TestByteRangeInputStream. Contributed by Plamen Jeliazkov. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1149770 Files : * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/namenode/TestStreamFile.java * /hadoop/common/trunk/hdfs/CHANGES.txt * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/TestByteRangeInputStream.java > Cleanup TestStreamFile and TestByteRangeInputStream > > > Key: HDFS-2116 > URL: https://issues.apache.org/jira/browse/HDFS-2116 > Project: Hadoop HDFS > Issue Type: Improvement > Components: test >Reporter: Eli Collins >Assignee: Plamen Jeliazkov >Priority: Minor > Labels: newbie > Attachments: HDFS-2116.patch, HDFS-2116.patch, HDFS-2116.patch, > HDFS-2116.patch, HDFS-2116[2].patch > > > TestStreamFile and TestByteRangeInputStream should use mockito. This would > allow the private URLOpener class to be removed from ByteRangeInputStream. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2112) Move ReplicationMonitor to block management
[ https://issues.apache.org/jira/browse/HDFS-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069949#comment-13069949 ] Hudson commented on HDFS-2112: -- Integrated in Hadoop-Hdfs-trunk #733 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/733/]) HDFS-2112. Move ReplicationMonitor to block management. Contributed by Uma Maheswara Rao G szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1149771 Files : * /hadoop/common/trunk/hdfs/src/test/unit/org/apache/hadoop/hdfs/server/namenode/TestNNLeaseRecovery.java * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/namenode/NameNodeAdapter.java * /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java * /hadoop/common/trunk/hdfs/CHANGES.txt * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/namenode/TestNodeCount.java * /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/blockmanagement/DecommissionManager.java * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/blockmanagement/BlockManagerTestUtil.java * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/namenode/TestLargeDirectoryDelete.java * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/namenode/NNThroughputBenchmark.java * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/namenode/TestBlockUnderConstruction.java * /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/NamenodeJspHelper.java * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/datanode/TestDataNodeVolumeFailure.java * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/namenode/TestComputeInvalidateWork.java * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/datanode/TestBlockReport.java * /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/namenode/TestOverReplicatedBlocks.java * /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java > Move ReplicationMonitor to block management > --- > > Key: HDFS-2112 > URL: https://issues.apache.org/jira/browse/HDFS-2112 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Uma Maheswara Rao G > Fix For: 0.23.0 > > Attachments: HDFS-2112.1.patch, HDFS-2112.patch > > > Replication should be handled by block manager instead of name system. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2191) Move datanodeMap from FSNamesystem to DatanodeManager
[ https://issues.apache.org/jira/browse/HDFS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069935#comment-13069935 ] Hadoop QA commented on HDFS-2191: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12487585/h2191_20110723.patch against trunk revision 1149771. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 18 new or modified tests. -1 javadoc. The javadoc tool appears to have generated 2 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 core unit tests. +1 contrib tests. The patch passed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1002//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1002//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1002//console This message is automatically generated. > Move datanodeMap from FSNamesystem to DatanodeManager > - > > Key: HDFS-2191 > URL: https://issues.apache.org/jira/browse/HDFS-2191 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2191_20110723.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2191) Move datanodeMap from FSNamesystem to DatanodeManager
[ https://issues.apache.org/jira/browse/HDFS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069930#comment-13069930 ] Hadoop QA commented on HDFS-2191: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12487585/h2191_20110723.patch against trunk revision 1149771. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 18 new or modified tests. -1 javadoc. The javadoc tool appears to have generated 2 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 core unit tests. +1 contrib tests. The patch passed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1003//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1003//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1003//console This message is automatically generated. > Move datanodeMap from FSNamesystem to DatanodeManager > - > > Key: HDFS-2191 > URL: https://issues.apache.org/jira/browse/HDFS-2191 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2191_20110723.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1739) When DataNode throws DiskOutOfSpaceException, it will be helpfull to the user if we log the available volume size and configured block size.
[ https://issues.apache.org/jira/browse/HDFS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069924#comment-13069924 ] Hudson commented on HDFS-1739: -- Integrated in Hadoop-Hdfs-trunk-Commit #802 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/802/]) HDFS-1739. Add available volume size to the error message when datanode throws DiskOutOfSpaceException. Contributed by Uma Maheswara Rao G szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1150067 Files : * /hadoop/common/trunk/hdfs/CHANGES.txt * /hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/datanode/TestRoundRobinVolumesPolicy.java * /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/datanode/RoundRobinVolumesPolicy.java > When DataNode throws DiskOutOfSpaceException, it will be helpfull to the user > if we log the available volume size and configured block size. > > > Key: HDFS-1739 > URL: https://issues.apache.org/jira/browse/HDFS-1739 > Project: Hadoop HDFS > Issue Type: Improvement > Components: data-node >Affects Versions: 0.23.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G >Priority: Minor > Fix For: 0.23.0 > > Attachments: HDFS-1739.1.patch, HDFS-1739.2.patch, HDFS-1739.3.patch, > HDFS-1739.4.patch, HDFS-1739.5.patch, HDFS-1739.patch > > > DataNode will throw DiskOutOfSpaceException for new blcok write if available > volume size is less than configured blcok size. > So, it will be helpfull to the user if we log this details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1739) When DataNode throws DiskOutOfSpaceException, it will be helpfull to the user if we log the available volume size and configured block size.
[ https://issues.apache.org/jira/browse/HDFS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1739: - Resolution: Fixed Fix Version/s: 0.23.0 Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) +1 patch looks good. I have committed this. Thanks, Uma! > When DataNode throws DiskOutOfSpaceException, it will be helpfull to the user > if we log the available volume size and configured block size. > > > Key: HDFS-1739 > URL: https://issues.apache.org/jira/browse/HDFS-1739 > Project: Hadoop HDFS > Issue Type: Improvement > Components: data-node >Affects Versions: 0.23.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G >Priority: Minor > Fix For: 0.23.0 > > Attachments: HDFS-1739.1.patch, HDFS-1739.2.patch, HDFS-1739.3.patch, > HDFS-1739.4.patch, HDFS-1739.5.patch, HDFS-1739.patch > > > DataNode will throw DiskOutOfSpaceException for new blcok write if available > volume size is less than configured blcok size. > So, it will be helpfull to the user if we log this details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2191) Move datanodeMap from FSNamesystem to DatanodeManager
[ https://issues.apache.org/jira/browse/HDFS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2191: - Attachment: h2191_20110723.patch h2191_20110723.patch: 1st patch > Move datanodeMap from FSNamesystem to DatanodeManager > - > > Key: HDFS-2191 > URL: https://issues.apache.org/jira/browse/HDFS-2191 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2191_20110723.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2191) Move datanodeMap from FSNamesystem to DatanodeManager
[ https://issues.apache.org/jira/browse/HDFS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2191: - Status: Patch Available (was: Open) > Move datanodeMap from FSNamesystem to DatanodeManager > - > > Key: HDFS-2191 > URL: https://issues.apache.org/jira/browse/HDFS-2191 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h2191_20110723.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2191) Move datanodeMap from FSNamesystem to DatanodeManager
Move datanodeMap from FSNamesystem to DatanodeManager - Key: HDFS-2191 URL: https://issues.apache.org/jira/browse/HDFS-2191 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Tsz Wo (Nicholas), SZE Assignee: Tsz Wo (Nicholas), SZE -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2158) Add JournalSet to manage the set of journals.
[ https://issues.apache.org/jira/browse/HDFS-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-2158: --- Attachment: HDFS-2158.1.patch This patch is on top of HDFS-1073 and HDFS-2018. > Add JournalSet to manage the set of journals. > - > > Key: HDFS-2158 > URL: https://issues.apache.org/jira/browse/HDFS-2158 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Fix For: 0.23.0 > > Attachments: HDFS-2158.1.patch > > > The management of the collection of journals can be encapsulated in a > JournalSet. This will cleanup the FSEditLog code significantly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
