[jira] [Commented] (HDFS-2264) NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo annotation

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

[jira] [Updated] (HDFS-4285) During the HttpServer start, the network card is forbidden, will through the exception "Port is i use". But the fact is that ""the requested local address could not be ass

[ https://issues.apache.org/jira/browse/HDFS-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuyang updated HDFS-4285: -- Attachment: HttpServer.java.patch > During the HttpServer start, the network card is forbidden, will through

[jira] [Created] (HDFS-4285) During the HttpServer start, the network card is forbidden, will through the exception "Port is i use". But the fact is that ""the requested local address could not be ass

liuyang created HDFS-4285: - Summary: During the HttpServer start, the network card is forbidden, will through the exception "Port is i use". But the fact is that ""the requested local address could not be assigned Key: HDFS-4285

[jira] [Commented] (HDFS-4045) SecondaryNameNode cannot read from QuorumJournal URI

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

[jira] [Updated] (HDFS-2264) NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo annotation

[ https://issues.apache.org/jira/browse/HDFS-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-2264: - Target Version/s: 2.0.3-alpha Affects Version/s: (was: 0.23.0) 2.0.

[jira] [Updated] (HDFS-2264) NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo annotation

[ https://issues.apache.org/jira/browse/HDFS-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-2264: - Status: Patch Available (was: Open) > NamenodeProtocol has the wrong value for clientPrincipa

[jira] [Assigned] (HDFS-2264) NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo annotation

[ https://issues.apache.org/jira/browse/HDFS-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers reassigned HDFS-2264: Assignee: Aaron T. Myers (was: Harsh J) > NamenodeProtocol has the wrong value for clie

[jira] [Updated] (HDFS-2264) NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo annotation

[ https://issues.apache.org/jira/browse/HDFS-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-2264: - Attachment: HDFS-2264.patch Here's a patch which addresses the issue by removing the clientPrincip

[jira] [Commented] (HDFS-3875) Issue handling checksum errors in write pipeline

[ https://issues.apache.org/jira/browse/HDFS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526101#comment-13526101 ] Kihwal Lee commented on HDFS-3875: -- Test failures are not caused by this patch. HDFS-4282,

[jira] [Commented] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length

[ https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526079#comment-13526079 ] Alejandro Abdelnur commented on HDFS-4236: -- Test failure is unrelated. Allen, ap

[jira] [Updated] (HDFS-1943) fail to start datanode while start-dfs.sh is executed by root user

[ https://issues.apache.org/jira/browse/HDFS-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shaposhnik updated HDFS-1943: --- Attachment: (was: 0001-HDFS-1943.-fail-to-start-datanode-while-start-dfs.sh.patch) >

[jira] [Updated] (HDFS-1943) fail to start datanode while start-dfs.sh is executed by root user

[ https://issues.apache.org/jira/browse/HDFS-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shaposhnik updated HDFS-1943: --- Attachment: 0001-HDFS-1943.-fail-to-start-datanode-while-start-dfs.sh.patch > fail to star

[jira] [Commented] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length

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

[jira] [Commented] (HDFS-4282) TestEditLog.testFuzzSequences FAILED in all pre-commit test

[ https://issues.apache.org/jira/browse/HDFS-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526073#comment-13526073 ] Aaron T. Myers commented on HDFS-4282: -- +1, the patch looks good to me. Thanks a lot,

[jira] [Updated] (HDFS-4045) SecondaryNameNode cannot read from QuorumJournal URI

[ https://issues.apache.org/jira/browse/HDFS-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Isaacson updated HDFS-4045: Attachment: hdfs4045-8.txt New patch, -8. - Use readFully rather than read to address Findbugs warni

[jira] [Commented] (HDFS-3875) Issue handling checksum errors in write pipeline

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

[jira] [Resolved] (HDFS-3984) TestAuditLogs#testAuditWebHdfs flaky

[ https://issues.apache.org/jira/browse/HDFS-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins resolved HDFS-3984. --- Resolution: Duplicate HDFS-4055 ended up fixing this. > TestAuditLogs#testAuditWebHdf

[jira] [Commented] (HDFS-4273) Problem in DFSInputStream read retry logic may cause early failure

[ https://issues.apache.org/jira/browse/HDFS-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526065#comment-13526065 ] Binglin Chang commented on HDFS-4273: - the failed test is caused by HDFS-4282

[jira] [Commented] (HDFS-4282) TestEditLog.testFuzzSequences FAILED in all pre-commit test

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

[jira] [Commented] (HDFS-3984) TestAuditLogs#testAuditWebHdfs flaky

[ https://issues.apache.org/jira/browse/HDFS-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526042#comment-13526042 ] David S. Wang commented on HDFS-3984: - This looks like a dup of HDFS-4055.

[jira] [Commented] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length

[ https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526036#comment-13526036 ] Suresh Srinivas commented on HDFS-4236: --- +1 for the change Alejandro. Thank you for m

[jira] [Updated] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length

[ https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated HDFS-4236: - Status: Patch Available (was: Open) > Regression: HDFS-4171 puts artificial limit on

[jira] [Updated] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length

[ https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated HDFS-4236: - Attachment: HDFS-4171.patch Patch that removes the limit on 31 chars. I was missing the p

[jira] [Assigned] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length

[ https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur reassigned HDFS-4236: Assignee: Alejandro Abdelnur > Regression: HDFS-4171 puts artificial limit on us

[jira] [Commented] (HDFS-4260) incorrect inclusion of drive spec in test root path causes multiple HDFS test failures on Windows

[ https://issues.apache.org/jira/browse/HDFS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526013#comment-13526013 ] Chris Nauroth commented on HDFS-4260: - The test failure mentioned by Jenkins is unrelat

[jira] [Commented] (HDFS-4260) incorrect inclusion of drive spec in test root path causes multiple HDFS test failures on Windows

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

[jira] [Commented] (HDFS-4256) Support for concatenation of files into a single file in branch-1

[ https://issues.apache.org/jira/browse/HDFS-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13525989#comment-13525989 ] Suresh Srinivas commented on HDFS-4256: --- Some comments: # In javadoc when referencing

[jira] [Created] (HDFS-4284) BlockReaderLocal not notified of failed disks

Andy Isaacson created HDFS-4284: --- Summary: BlockReaderLocal not notified of failed disks Key: HDFS-4284 URL: https://issues.apache.org/jira/browse/HDFS-4284 Project: Hadoop HDFS Issue Type: Bug

[jira] [Commented] (HDFS-4239) Means of telling the datanode to stop using a sick disk

[ https://issues.apache.org/jira/browse/HDFS-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13525888#comment-13525888 ] Andy Isaacson commented on HDFS-4239: - I created HDFS-4284 to track the BlockReaderLoca

[jira] [Updated] (HDFS-4282) TestEditLog.testFuzzSequences FAILED in all pre-commit test

[ https://issues.apache.org/jira/browse/HDFS-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-4282: -- Status: Patch Available (was: Open) > TestEditLog.testFuzzSequences FAILED in all pre-commit test >

[jira] [Commented] (HDFS-3680) Allow customized audit logging in HDFS FSNamesystem

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

[jira] [Updated] (HDFS-3875) Issue handling checksum errors in write pipeline

[ https://issues.apache.org/jira/browse/HDFS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-3875: - Attachment: hdfs-3875.trunk.patch.txt The new patch addresses the review comments. {{checksumError}} is no

[jira] [Updated] (HDFS-3680) Allow customized audit logging in HDFS FSNamesystem

[ https://issues.apache.org/jira/browse/HDFS-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-3680: - Resolution: Fixed Fix Version/s: 2.0.3-alpha Hadoop Flags: Reviewed Status:

[jira] [Commented] (HDFS-3680) Allow customized audit logging in HDFS FSNamesystem

[ https://issues.apache.org/jira/browse/HDFS-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13525815#comment-13525815 ] Suresh Srinivas commented on HDFS-3680: --- I have no further comments. The patch looks

[jira] [Commented] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length

[ https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13525434#comment-13525434 ] Suresh Srinivas commented on HDFS-4236: --- bq. I think that is a bigger issue than the

[jira] [Updated] (HDFS-4260) incorrect inclusion of drive spec in test root path causes multiple HDFS test failures on Windows

[ https://issues.apache.org/jira/browse/HDFS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4260: Status: Patch Available (was: Open) > incorrect inclusion of drive spec in test root path cause

[jira] [Updated] (HDFS-4260) incorrect inclusion of drive spec in test root path causes multiple HDFS test failures on Windows

[ https://issues.apache.org/jira/browse/HDFS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4260: Target Version/s: 3.0.0, trunk-win (was: trunk-win) Affects Version/s: 3.0.0 Adding 3.0.0 to A

[jira] [Updated] (HDFS-4260) incorrect inclusion of drive spec in test root path causes multiple HDFS test failures on Windows

[ https://issues.apache.org/jira/browse/HDFS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4260: Attachment: HDFS-4260-branch-trunk-win.3.patch Thanks, Sanjay. I am uploading version 3 of the patc

[jira] [Commented] (HDFS-4171) WebHDFS and HttpFs should accept only valid Unix user names

[ https://issues.apache.org/jira/browse/HDFS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512066#comment-13512066 ] Alejandro Abdelnur commented on HDFS-4171: -- Cross-posting with HDFS-4236: ---

[jira] [Commented] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length

[ https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512064#comment-13512064 ] Alejandro Abdelnur commented on HDFS-4236: -- Suresh, without HDFS-4171 usernames co

[jira] [Commented] (HDFS-4171) WebHDFS and HttpFs should accept only valid Unix user names

[ https://issues.apache.org/jira/browse/HDFS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512037#comment-13512037 ] Suresh Srinivas commented on HDFS-4171: --- Posting my comments from HDFS-4236: This jir

[jira] [Commented] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length

[ https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512036#comment-13512036 ] Suresh Srinivas commented on HDFS-4236: --- This jira is essentially makes comments on t

[jira] [Commented] (HDFS-4260) incorrect inclusion of drive spec in test root path causes multiple HDFS test failures on Windows

[ https://issues.apache.org/jira/browse/HDFS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512021#comment-13512021 ] Sanjay Radia commented on HDFS-4260: There is a better way to fix this. See HADOOP-8487

[jira] [Commented] (HDFS-4282) TestEditLog.testFuzzSequences FAILED in all pre-commit test

[ https://issues.apache.org/jira/browse/HDFS-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512013#comment-13512013 ] Colin Patrick McCabe commented on HDFS-4282: There's another option which you m

[jira] [Resolved] (HDFS-4283) Spurious Test failures in TestEditLog.testFuzzSequences

[ https://issues.apache.org/jira/browse/HDFS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe resolved HDFS-4283. Resolution: Duplicate > Spurious Test failures in TestEditLog.testFuzzSequences

[jira] [Commented] (HDFS-4275) MiniDFSCluster-based tests fail on Windows due to failure to delete test name node directory

[ https://issues.apache.org/jira/browse/HDFS-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511576#comment-13511576 ] Chris Nauroth commented on HDFS-4275: - This is partially caused by the test timeout in

[jira] [Commented] (HDFS-4273) Problem in DFSInputStream read retry logic may cause early failure

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

[jira] [Updated] (HDFS-4270) Replications of the highest priority should be allowed to choose a source datanode that has reached its max replication limit

[ https://issues.apache.org/jira/browse/HDFS-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Dagit updated HDFS-4270: -- Status: Open (was: Patch Available) Canceling patch for now. Later after discussion, I'll fix the erro

[jira] [Commented] (HDFS-4270) Replications of the highest priority should be allowed to choose a source datanode that has reached its max replication limit

[ https://issues.apache.org/jira/browse/HDFS-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511534#comment-13511534 ] Derek Dagit commented on HDFS-4270: --- Hi Aaron, Noted. I meant to remove the entries in

[jira] [Updated] (HDFS-4282) TestEditLog.testFuzzSequences FAILED in all pre-commit test

[ https://issues.apache.org/jira/browse/HDFS-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-4282: -- Attachment: hdfs-4282.txt Here's a patch which implements a toStringChecked() method. I also had to add

[jira] [Updated] (HDFS-4273) Problem in DFSInputStream read retry logic may cause early failure

[ https://issues.apache.org/jira/browse/HDFS-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated HDFS-4273: Attachment: HDFS-4273-v2.patch new version, fix bug -- forget to set blockEnd to -1 in two places:

[jira] [Commented] (HDFS-4270) Replications of the highest priority should be allowed to choose a source datanode that has reached its max replication limit

[ https://issues.apache.org/jira/browse/HDFS-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511433#comment-13511433 ] Daryn Sharp commented on HDFS-4270: --- I don't fully understand this subsystem, but I'm a b

[jira] [Commented] (HDFS-4238) [HA] Standby namenode should not do purging of shared storage edits.

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

[jira] [Commented] (HDFS-4234) Use the generic code for choosing datanode in Balancer

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

[jira] [Commented] (HDFS-4199) Provide test for HdfsVolumeId

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

[jira] [Commented] (HDFS-4240) In nodegroup-aware case, make sure nodes are avoided to place replica if some replica are already under the same nodegroup

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

[jira] [Commented] (HDFS-4268) Remove redundant enum NNHAStatusHeartbeat.State

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

[jira] [Commented] (HDFS-4243) INodeDirectory.replaceChild(..) does not update parent

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

[jira] [Commented] (HDFS-2802) Support for RW/RO snapshots in HDFS

[ https://issues.apache.org/jira/browse/HDFS-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511344#comment-13511344 ] Hudson commented on HDFS-2802: -- Integrated in Hadoop-Hdfs-Snapshots-Branch-build #31 (See [ht

[jira] [Updated] (HDFS-4273) Problem in DFSInputStream read retry logic may cause early failure

[ https://issues.apache.org/jira/browse/HDFS-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated HDFS-4273: Attachment: HDFS-4273.patch I am referring read() as int readWithStrategy(ReaderStrategy strategy, i

[jira] [Updated] (HDFS-4273) Problem in DFSInputStream read retry logic may cause early failure

[ https://issues.apache.org/jira/browse/HDFS-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated HDFS-4273: Status: Patch Available (was: Open) > Problem in DFSInputStream read retry logic may cause earl

[jira] [Commented] (HDFS-4238) [HA] Standby namenode should not do purging of shared storage edits.

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

[jira] [Commented] (HDFS-4234) Use the generic code for choosing datanode in Balancer

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

[jira] [Commented] (HDFS-4240) In nodegroup-aware case, make sure nodes are avoided to place replica if some replica are already under the same nodegroup

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

[jira] [Commented] (HDFS-4268) Remove redundant enum NNHAStatusHeartbeat.State

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

[jira] [Commented] (HDFS-4199) Provide test for HdfsVolumeId

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

[jira] [Commented] (HDFS-4243) INodeDirectory.replaceChild(..) does not update parent

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

[jira] [Commented] (HDFS-4261) TestBalancerWithNodeGroup times out

[ https://issues.apache.org/jira/browse/HDFS-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511228#comment-13511228 ] Junping Du commented on HDFS-4261: -- Thanks ATM for the important reminder!

[jira] [Commented] (HDFS-4261) TestBalancerWithNodeGroup times out

[ https://issues.apache.org/jira/browse/HDFS-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511219#comment-13511219 ] Aaron T. Myers commented on HDFS-4261: -- Thanks, Junping. The way you addressed my comm

[jira] [Commented] (HDFS-4279) NameNode does not initialize generic conf keys when started with -recover

[ https://issues.apache.org/jira/browse/HDFS-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511218#comment-13511218 ] Aaron T. Myers commented on HDFS-4279: -- The patch looks good to me. +1 pending Jenkins

[jira] [Updated] (HDFS-4261) TestBalancerWithNodeGroup times out

[ https://issues.apache.org/jira/browse/HDFS-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HDFS-4261: - Attachment: HDFS-4261-v4.patch Address ATM's comments to fix a bug involved in previous JIRA patch.

[jira] [Commented] (HDFS-4282) TestEditLog.testFuzzSequences FAILED in all pre-commit test

[ https://issues.apache.org/jira/browse/HDFS-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511213#comment-13511213 ] Junping Du commented on HDFS-4282: -- Yes. Option 2 seems to be a better way.