[jira] [Commented] (HDFS-5663) make the retry time and interval value configurable in openInfo()

[ https://issues.apache.org/jira/browse/HDFS-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850202#comment-13850202 ] Hadoop QA commented on HDFS-5663: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850195#comment-13850195 ] Jing Zhao commented on HDFS-5496: - Thanks Vinay! The new patch looks good to me. [~kihwal],

[jira] [Commented] (HDFS-5671) When Hbase RegionServer request block to DataNode and "java.io.IOException" occurs, the fail TCP socket is not closed (in status "CLOSE_WAIT" with port 1004 of DataNode)

[ https://issues.apache.org/jira/browse/HDFS-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850152#comment-13850152 ] JamesLi commented on HDFS-5671: --- @stack I have add the patch file,but we haven't test yet. Ac

[jira] [Updated] (HDFS-5671) When Hbase RegionServer request block to DataNode and "java.io.IOException" occurs, the fail TCP socket is not closed (in status "CLOSE_WAIT" with port 1004 of DataNode)

[ https://issues.apache.org/jira/browse/HDFS-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JamesLi updated HDFS-5671: -- Attachment: 5671.patch > When Hbase RegionServer request block to DataNode and "java.io.IOException" > occurs,

[jira] [Updated] (HDFS-5671) When Hbase RegionServer request block to DataNode and "java.io.IOException" occurs, the fail TCP socket is not closed (in status "CLOSE_WAIT" with port 1004 of DataNode)

[ https://issues.apache.org/jira/browse/HDFS-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JamesLi updated HDFS-5671: -- Status: Patch Available (was: Open) > When Hbase RegionServer request block to DataNode and "java.io.IOExceptio

[jira] [Updated] (HDFS-5671) When Hbase RegionServer request block to DataNode and "java.io.IOException" occurs, the fail TCP socket is not closed (in status "CLOSE_WAIT" with port 1004 of DataNode)

[ https://issues.apache.org/jira/browse/HDFS-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JamesLi updated HDFS-5671: -- Description: lsof -i TCP:1004 | grep -c CLOSE_WAIT 18235 When hbase regionserver request a file's block to DataN

[jira] [Commented] (HDFS-5431) support cachepool-based limit management in path-based caching

[ https://issues.apache.org/jira/browse/HDFS-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850116#comment-13850116 ] Hadoop QA commented on HDFS-5431: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (HDFS-5663) make the retry time and interval value configurable in openInfo()

[ https://issues.apache.org/jira/browse/HDFS-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HDFS-5663: Attachment: HDFS-5663.txt Retry > make the retry time and interval value configurable in openInfo() > -

[jira] [Commented] (HDFS-5671) When Hbase RegionServer request block to DataNode and "java.io.IOException" occurs, the fail TCP socket is not closed (in status "CLOSE_WAIT" with port 1004 of DataNode)

[ https://issues.apache.org/jira/browse/HDFS-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850100#comment-13850100 ] stack commented on HDFS-5671: - Would you have a patch [~jamesli]? If so, would you mind postin

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850091#comment-13850091 ] Hadoop QA commented on HDFS-5496: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-5442) Zero loss HDFS data replication for multiple datacenters

[ https://issues.apache.org/jira/browse/HDFS-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850052#comment-13850052 ] Liang Xie commented on HDFS-5442: - [~liulei], your solution can not have a low enough laten

[jira] [Updated] (HDFS-5671) When Hbase RegionServer request block to DataNode and "java.io.IOException" occurs, the fail TCP socket is not closed (in status "CLOSE_WAIT" with port 1004 of DataNode)

[ https://issues.apache.org/jira/browse/HDFS-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JamesLi updated HDFS-5671: -- Priority: Critical (was: Major) > When Hbase RegionServer request block to DataNode and "java.io.IOException"

[jira] [Commented] (HDFS-5634) allow BlockReaderLocal to switch between checksumming and not

[ https://issues.apache.org/jira/browse/HDFS-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850001#comment-13850001 ] Andrew Wang commented on HDFS-5634: --- +1, thanks for all the revs Colin. If we find any mo

[jira] [Commented] (HDFS-5431) support cachepool-based limit management in path-based caching

[ https://issues.apache.org/jira/browse/HDFS-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849989#comment-13849989 ] Colin Patrick McCabe commented on HDFS-5431: +1 pending jenkins. > support cac

[jira] [Updated] (HDFS-5431) support cachepool-based limit management in path-based caching

[ https://issues.apache.org/jira/browse/HDFS-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-5431: -- Attachment: hdfs-5431-7.patch Thanks, fixed the stubby method and adjusted the findbugs exclude file. Le

[jira] [Commented] (HDFS-5634) allow BlockReaderLocal to switch between checksumming and not

[ https://issues.apache.org/jira/browse/HDFS-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849971#comment-13849971 ] Hadoop QA commented on HDFS-5634: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5496: Attachment: HDFS-5496.patch Here is updated patch > Make replication queue initialization asynchronous > --

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849961#comment-13849961 ] Vinay commented on HDFS-5496: - Thanks for the explanation Jing. I knew I missed something. Now

[jira] [Updated] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-5350: -- Resolution: Fixed Fix Version/s: (was: 3.0.0) 2.4.0 Hadoop Flags: Revi

[jira] [Commented] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849934#comment-13849934 ] Hudson commented on HDFS-5350: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4896 (See [https:

[jira] [Resolved] (HDFS-5566) HA namenode with QJM created from org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider should implement Closeable

[ https://issues.apache.org/jira/browse/HDFS-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang resolved HDFS-5566. --- Resolution: Invalid Looked into it and found out that it is an HBase issue actually. HDFS is good. >

[jira] [Commented] (HDFS-5431) support cachepool-based limit management in path-based caching

[ https://issues.apache.org/jira/browse/HDFS-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849875#comment-13849875 ] Hadoop QA commented on HDFS-5431: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849833#comment-13849833 ] Hadoop QA commented on HDFS-5350: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-5634) allow BlockReaderLocal to switch between checksumming and not

[ https://issues.apache.org/jira/browse/HDFS-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-5634: --- Attachment: HDFS-5634.007.patch > allow BlockReaderLocal to switch between checksummin

[jira] [Commented] (HDFS-5634) allow BlockReaderLocal to switch between checksumming and not

[ https://issues.apache.org/jira/browse/HDFS-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849805#comment-13849805 ] Colin Patrick McCabe commented on HDFS-5634: Another problem related to changin

[jira] [Commented] (HDFS-5431) support cachepool-based limit management in path-based caching

[ https://issues.apache.org/jira/browse/HDFS-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849796#comment-13849796 ] Colin Patrick McCabe commented on HDFS-5431: Thanks. This looks a lot better w

[jira] [Commented] (HDFS-5242) Reduce contention on DatanodeInfo instances

[ https://issues.apache.org/jira/browse/HDFS-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849771#comment-13849771 ] Suresh Srinivas commented on HDFS-5242: --- I am not sure how much performance impact th

[jira] [Commented] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849752#comment-13849752 ] Andrew Wang commented on HDFS-5350: --- +1 pending Jenkins, thanks Jimmy. > Name Node shoul

[jira] [Commented] (HDFS-5634) allow BlockReaderLocal to switch between checksumming and not

[ https://issues.apache.org/jira/browse/HDFS-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849751#comment-13849751 ] Hadoop QA commented on HDFS-5634: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-5431) support cachepool-based limit management in path-based caching

[ https://issues.apache.org/jira/browse/HDFS-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849744#comment-13849744 ] Andrew Wang commented on HDFS-5431: --- Thanks for the reviews, v6 attached. Changes are onl

[jira] [Updated] (HDFS-5431) support cachepool-based limit management in path-based caching

[ https://issues.apache.org/jira/browse/HDFS-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-5431: -- Attachment: hdfs-5431-6.patch > support cachepool-based limit management in path-based caching > ---

[jira] [Updated] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HDFS-5350: -- Attachment: trunk-5350_v3.patch Attached patch v3, moved the test to TestCheckpoint. It is hard to predi

[jira] [Updated] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HDFS-5350: -- Status: Patch Available (was: Open) > Name Node should report fsimage transfer time as a metric > -

[jira] [Commented] (HDFS-5434) Write resiliency for replica count 1

[ https://issues.apache.org/jira/browse/HDFS-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849701#comment-13849701 ] Eric Sirianni commented on HDFS-5434: - Thanks everyone for all the good technical feedb

[jira] [Commented] (HDFS-5595) NameNode: implement AclManager as abstraction over INode ACL Map.

[ https://issues.apache.org/jira/browse/HDFS-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849675#comment-13849675 ] Chris Nauroth commented on HDFS-5595: - This work is on hold for now, because the work o

[jira] [Work started] (HDFS-5673) Implement logic for modification of ACLs.

[ https://issues.apache.org/jira/browse/HDFS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-5673 started by Chris Nauroth. > Implement logic for modification of ACLs. > - > > Key: HDFS-5673 >

[jira] [Created] (HDFS-5673) Implement logic for modification of ACLs.

Chris Nauroth created HDFS-5673: --- Summary: Implement logic for modification of ACLs. Key: HDFS-5673 URL: https://issues.apache.org/jira/browse/HDFS-5673 Project: Hadoop HDFS Issue Type: Sub-tas

[jira] [Work started] (HDFS-5595) NameNode: implement AclManager as abstraction over INode ACL Map.

[ https://issues.apache.org/jira/browse/HDFS-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-5595 started by Chris Nauroth. > NameNode: implement AclManager as abstraction over INode ACL Map. > -

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849670#comment-13849670 ] Jing Zhao commented on HDFS-5496: - bq. So it can completely miss initialization of replicat

[jira] [Commented] (HDFS-5434) Write resiliency for replica count 1

[ https://issues.apache.org/jira/browse/HDFS-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849642#comment-13849642 ] Arpit Agarwal commented on HDFS-5434: - I meant by using a _custom_ BlockPlacementPolicy

[jira] [Commented] (HDFS-5434) Write resiliency for replica count 1

[ https://issues.apache.org/jira/browse/HDFS-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849639#comment-13849639 ] Arpit Agarwal commented on HDFS-5434: - Thanks for the explanation, Colin and Eric. In

[jira] [Commented] (HDFS-5657) race condition causes writeback state error in NFS gateway

[ https://issues.apache.org/jira/browse/HDFS-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849631#comment-13849631 ] Hadoop QA commented on HDFS-5657: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (HDFS-5634) allow BlockReaderLocal to switch between checksumming and not

[ https://issues.apache.org/jira/browse/HDFS-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-5634: --- Attachment: HDFS-5634.006.patch * Fixed a bug introduced by converting to using skipCh

[jira] [Commented] (HDFS-5657) race condition causes writeback state error in NFS gateway

[ https://issues.apache.org/jira/browse/HDFS-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849600#comment-13849600 ] Brandon Li commented on HDFS-5657: -- [~jingzhao], as you pointed out offline, it may be an

[jira] [Updated] (HDFS-5657) race condition causes writeback state error in NFS gateway

[ https://issues.apache.org/jira/browse/HDFS-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Li updated HDFS-5657: - Attachment: HDFS-5657.new.001.patch > race condition causes writeback state error in NFS gateway > ---

[jira] [Commented] (HDFS-5434) Write resiliency for replica count 1

[ https://issues.apache.org/jira/browse/HDFS-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849577#comment-13849577 ] Suresh Srinivas commented on HDFS-5434: --- Some comments: bq. Server-side enforcement o

[jira] [Commented] (HDFS-5666) Fix inconsistent synchronization in BPOfferService

[ https://issues.apache.org/jira/browse/HDFS-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849451#comment-13849451 ] Hudson commented on HDFS-5666: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4890 (See [https:

[jira] [Updated] (HDFS-5666) Fix inconsistent synchronization in BPOfferService

[ https://issues.apache.org/jira/browse/HDFS-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-5666: --- Resolution: Fixed Fix Version/s: 2.3.0 Target Version/s: 2.3.0

[jira] [Commented] (HDFS-5454) DataNode UUID should be assigned prior to FsDataset initialization

[ https://issues.apache.org/jira/browse/HDFS-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849433#comment-13849433 ] Hudson commented on HDFS-5454: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4889 (See [https:

[jira] [Commented] (HDFS-5666) Fix inconsistent synchronization in BPOfferService

[ https://issues.apache.org/jira/browse/HDFS-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849427#comment-13849427 ] Colin Patrick McCabe commented on HDFS-5666: +1. thanks, Jimmy. > Fix inconsi

[jira] [Updated] (HDFS-5666) Fix inconsistent synchronization in BPOfferService

[ https://issues.apache.org/jira/browse/HDFS-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-5666: --- Description: TestBPOfferService#testBPInitErrorHandling fails intermittently. We beli

[jira] [Updated] (HDFS-5666) Fix inconsistent synchronization in BPOfferService

[ https://issues.apache.org/jira/browse/HDFS-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-5666: --- Summary: Fix inconsistent synchronization in BPOfferService (was: TestBPOfferService#

[jira] [Updated] (HDFS-5454) DataNode UUID should be assigned prior to FsDataset initialization

[ https://issues.apache.org/jira/browse/HDFS-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-5454: Resolution: Fixed Fix Version/s: 3.0.0 Hadoop Flags: Reviewed Status: Resolved

[jira] [Commented] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849387#comment-13849387 ] Jimmy Xiang commented on HDFS-5350: --- Sorry, wrong patch. I see. Let me take a look TestCh

[jira] [Updated] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HDFS-5350: -- Attachment: (was: trunk-5666_v2.patch) > Name Node should report fsimage transfer time as a metric >

[jira] [Commented] (HDFS-5661) Browsing FileSystem via web ui, should use datanode's hostname instead of ip address

[ https://issues.apache.org/jira/browse/HDFS-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849381#comment-13849381 ] Benoy Antony commented on HDFS-5661: DelegationToken is used to access Namenode. Here

[jira] [Commented] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849380#comment-13849380 ] Andrew Wang commented on HDFS-5350: --- Hi Jimmy, I think you might have attached the wrong

[jira] [Updated] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HDFS-5350: -- Attachment: trunk-5666_v2.patch Andrew, thanks a lot for the review. I fixed the GetImage metric. I als

[jira] [Updated] (HDFS-5350) Name Node should report fsimage transfer time as a metric

[ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HDFS-5350: -- Status: Open (was: Patch Available) > Name Node should report fsimage transfer time as a metric > -

[jira] [Commented] (HDFS-5665) Remove the unnecessary writeLock while initializing CacheManager in FsNameSystem Ctor

[ https://issues.apache.org/jira/browse/HDFS-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849355#comment-13849355 ] Hudson commented on HDFS-5665: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4887 (See [https:

[jira] [Updated] (HDFS-5665) Remove the unnecessary writeLock while initializing CacheManager in FsNameSystem Ctor

[ https://issues.apache.org/jira/browse/HDFS-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-5665: -- Resolution: Fixed Fix Version/s: 3.0.0 Hadoop Flags: Reviewed Status: Resolved (w

[jira] [Commented] (HDFS-5442) Zero loss HDFS data replication for multiple datacenters

[ https://issues.apache.org/jira/browse/HDFS-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849350#comment-13849350 ] Lohit Vijayarenu commented on HDFS-5442: Thanks for sharing the design document. Th

[jira] [Commented] (HDFS-5665) Remove the unnecessary writeLock while initializing CacheManager in FsNameSystem Ctor

[ https://issues.apache.org/jira/browse/HDFS-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849338#comment-13849338 ] Andrew Wang commented on HDFS-5665: --- These test failures look spurious to me. +1, thanks

[jira] [Commented] (HDFS-5665) Remove the unnecessary writeLock while initializing CacheManager in FsNameSystem Ctor

[ https://issues.apache.org/jira/browse/HDFS-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849306#comment-13849306 ] Hadoop QA commented on HDFS-5665: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-5434) Write resiliency for replica count 1

[ https://issues.apache.org/jira/browse/HDFS-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849234#comment-13849234 ] Taylor, Buddy commented on HDFS-5434: - Nice update, thanks. > Write resiliency for

[jira] [Created] (HDFS-5672) TestHASafeMode#testSafeBlockTracking fails in trunk

Ted Yu created HDFS-5672: Summary: TestHASafeMode#testSafeBlockTracking fails in trunk Key: HDFS-5672 URL: https://issues.apache.org/jira/browse/HDFS-5672 Project: Hadoop HDFS Issue Type: Test

[jira] [Commented] (HDFS-5592) "DIR* completeFile: /file is closed by DFSClient_" should be logged only for successful closure of the file.

[ https://issues.apache.org/jira/browse/HDFS-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849204#comment-13849204 ] Hudson commented on HDFS-5592: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1640 (See [htt

[jira] [Commented] (HDFS-5406) Send incremental block reports for all storages in a single call

[ https://issues.apache.org/jira/browse/HDFS-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849205#comment-13849205 ] Hudson commented on HDFS-5406: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1640 (See [htt

[jira] [Commented] (HDFS-5592) "DIR* completeFile: /file is closed by DFSClient_" should be logged only for successful closure of the file.

[ https://issues.apache.org/jira/browse/HDFS-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849147#comment-13849147 ] Hudson commented on HDFS-5592: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1614 (See [https://

[jira] [Commented] (HDFS-5406) Send incremental block reports for all storages in a single call

[ https://issues.apache.org/jira/browse/HDFS-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849148#comment-13849148 ] Hudson commented on HDFS-5406: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1614 (See [https://

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849110#comment-13849110 ] Hadoop QA commented on HDFS-5496: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-5665) Remove the unnecessary writeLock while initializing CacheManager in FsNameSystem Ctor

[ https://issues.apache.org/jira/browse/HDFS-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849069#comment-13849069 ] Hadoop QA commented on HDFS-5665: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-5592) "DIR* completeFile: /file is closed by DFSClient_" should be logged only for successful closure of the file.

[ https://issues.apache.org/jira/browse/HDFS-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849028#comment-13849028 ] Hudson commented on HDFS-5592: -- FAILURE: Integrated in Hadoop-Yarn-trunk #423 (See [https://b

[jira] [Commented] (HDFS-5406) Send incremental block reports for all storages in a single call

[ https://issues.apache.org/jira/browse/HDFS-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849029#comment-13849029 ] Hudson commented on HDFS-5406: -- FAILURE: Integrated in Hadoop-Yarn-trunk #423 (See [https://b

[jira] [Updated] (HDFS-5671) When Hbase RegionServer request block to DataNode and "java.io.IOException" occurs, the fail TCP socket is not closed (in status "CLOSE_WAIT" with port 1004 of DataNode)

[ https://issues.apache.org/jira/browse/HDFS-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JamesLi updated HDFS-5671: -- Remaining Estimate: (was: 1h) Original Estimate: (was: 1h) > When Hbase RegionServer request block

[jira] [Created] (HDFS-5671) When Hbase RegionServer request block to DataNode and "java.io.IOException" occurs, the fail TCP socket is not closed (in status "CLOSE_WAIT" with port 1004 of DataNode)

JamesLi created HDFS-5671: - Summary: When Hbase RegionServer request block to DataNode and "java.io.IOException" occurs, the fail TCP socket is not closed (in status "CLOSE_WAIT" with port 1004 of DataNode) Key: HDFS-5671

[jira] [Commented] (HDFS-5592) "DIR* completeFile: /file is closed by DFSClient_" should be logged only for successful closure of the file.

[ https://issues.apache.org/jira/browse/HDFS-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848993#comment-13848993 ] Hudson commented on HDFS-5592: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4886 (See [https:

[jira] [Commented] (HDFS-5592) "DIR* completeFile: /file is closed by DFSClient_" should be logged only for successful closure of the file.

[ https://issues.apache.org/jira/browse/HDFS-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848986#comment-13848986 ] Vinay commented on HDFS-5592: - Thanks Uma > "DIR* completeFile: /file is closed by DFSClient_"

[jira] [Updated] (HDFS-5592) "DIR* completeFile: /file is closed by DFSClient_" should be logged only for successful closure of the file.

[ https://issues.apache.org/jira/browse/HDFS-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-5592: -- Resolution: Fixed Fix Version/s: 2.3.0 3.0.0 Hadoop Flags:

[jira] [Updated] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5496: Attachment: HDFS-5496.patch Added missed change > Make replication queue initialization asynchronous >

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848975#comment-13848975 ] Hadoop QA commented on HDFS-5496: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-5442) Zero loss HDFS data replication for multiple datacenters

[ https://issues.apache.org/jira/browse/HDFS-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848966#comment-13848966 ] LiuLei commented on HDFS-5442: -- Hi Jerry,the design document is very good. There are two clu

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848962#comment-13848962 ] Vinay commented on HDFS-5496: - Also added a method to get the progress of initialization. Which

[jira] [Updated] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5496: Attachment: HDFS-5496.patch Attaching the patch with below changes. 1. Included reprocessing from startActiveService

[jira] [Commented] (HDFS-5389) A Namenode that keeps only a part of the namespace in memory

[ https://issues.apache.org/jira/browse/HDFS-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848952#comment-13848952 ] Satish Gopalani commented on HDFS-5389: --- Lin, Just out of curiosity. Is there any ini

[jira] [Updated] (HDFS-5665) Remove the unnecessary writeLock while initializing CacheManager in FsNameSystem Ctor

[ https://issues.apache.org/jira/browse/HDFS-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-5665: -- Status: Patch Available (was: Open) > Remove the unnecessary writeLock while initializi

[jira] [Updated] (HDFS-5665) Remove the unnecessary writeLock while initializing CacheManager in FsNameSystem Ctor

[ https://issues.apache.org/jira/browse/HDFS-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-5665: -- Attachment: HDFS-5665.patch > Remove the unnecessary writeLock while initializing CacheM

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848939#comment-13848939 ] Vinay commented on HDFS-5496: - {quote}How about changing this to {code}if (!isInSafeMode() || (