[jira] [Commented] (HDFS-4552) For Hadoop 2.0.3; setting CLASSPATH=$(hadoop classpath) does not work, as opposed to 1.x versions

[ https://issues.apache.org/jira/browse/HDFS-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231865#comment-14231865 ] Chris Nauroth commented on HDFS-4552: - Hello, [~shubhangi]. The reason for this

[jira] [Resolved] (HDFS-4552) For Hadoop 2.0.3; setting CLASSPATH=$(hadoop classpath) does not work, as opposed to 1.x versions

[ https://issues.apache.org/jira/browse/HDFS-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HDFS-4552. - Resolution: Duplicate For Hadoop 2.0.3; setting CLASSPATH=$(hadoop classpath) does not work, as

[jira] [Commented] (HDFS-7431) log message for InvalidMagicNumberException may be incorrect

[ https://issues.apache.org/jira/browse/HDFS-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231916#comment-14231916 ] Chris Nauroth commented on HDFS-7431: - Hi, Yi. This looks good. This is really minor,

[jira] [Commented] (HDFS-7188) support build libhdfs3 on windows

[ https://issues.apache.org/jira/browse/HDFS-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14232100#comment-14232100 ] Chris Nauroth commented on HDFS-7188: - I agree with the direction of using separately

[jira] [Commented] (HDFS-6833) DirectoryScanner should not register a deleting block with memory of DataNode

[ https://issues.apache.org/jira/browse/HDFS-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230078#comment-14230078 ] Chris Nauroth commented on HDFS-6833: - Hi [~sinchii]. Are you planning on posting an

[jira] [Commented] (HDFS-7384) 'getfacl' command and 'getAclStatus' output should be in sync

[ https://issues.apache.org/jira/browse/HDFS-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230131#comment-14230131 ] Chris Nauroth commented on HDFS-7384: - Thanks for the updated patch, Vinay. Nice, the

[jira] [Commented] (HDFS-7454) Implement Global ACL Set for memory optimization in NameNode

[ https://issues.apache.org/jira/browse/HDFS-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229266#comment-14229266 ] Chris Nauroth commented on HDFS-7454: - Last time I checked on this, an {{AclEntry}}

[jira] [Commented] (HDFS-7454) Implement Global ACL Set for memory optimization in NameNode

[ https://issues.apache.org/jira/browse/HDFS-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229454#comment-14229454 ] Chris Nauroth commented on HDFS-7454: - I actually think there is value in both

[jira] [Commented] (HDFS-7431) log message for InvalidMagicNumberException may be incorrect

[ https://issues.apache.org/jira/browse/HDFS-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226538#comment-14226538 ] Chris Nauroth commented on HDFS-7431: - Hello, Yi. Thank you for investigating this and

[jira] [Commented] (HDFS-7384) 'getfacl' command and 'getAclStatus' output should be in sync

[ https://issues.apache.org/jira/browse/HDFS-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226786#comment-14226786 ] Chris Nauroth commented on HDFS-7384: - Hi [~vinayrpet]. Thank you for the follow-up.

[jira] [Commented] (HDFS-7188) support build libhdfs3 on windows

[ https://issues.apache.org/jira/browse/HDFS-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223177#comment-14223177 ] Chris Nauroth commented on HDFS-7188: - Hi, [~thanhdo]. That sounds like an acceptable

[jira] [Created] (HDFS-7425) NameNode block deletion logging uses incorrect appender.

Chris Nauroth created HDFS-7425: --- Summary: NameNode block deletion logging uses incorrect appender. Key: HDFS-7425 URL: https://issues.apache.org/jira/browse/HDFS-7425 Project: Hadoop HDFS

[jira] [Updated] (HDFS-7425) NameNode block deletion logging uses incorrect appender.

[ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7425: Priority: Minor (was: Major) NameNode block deletion logging uses incorrect appender.

[jira] [Updated] (HDFS-7425) NameNode block deletion logging uses incorrect appender.

[ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7425: Attachment: HDFS-7425-branch-2.1.patch Here is a branch-2 patch that corrects this logging. This is

[jira] [Resolved] (HDFS-7425) NameNode block deletion logging uses incorrect appender.

[ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HDFS-7425. - Resolution: Fixed Fix Version/s: 2.6.1 Hadoop Flags: Reviewed I committed this to

[jira] [Commented] (HDFS-6833) DirectoryScanner should not register a deleting block with memory of DataNode

[ https://issues.apache.org/jira/browse/HDFS-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14216528#comment-14216528 ] Chris Nauroth commented on HDFS-6833: - Thank you for working on this, Shinichi.

[jira] [Commented] (HDFS-6833) DirectoryScanner should not register a deleting block with memory of DataNode

[ https://issues.apache.org/jira/browse/HDFS-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14216546#comment-14216546 ] Chris Nauroth commented on HDFS-6833: - Also related to the last comment, are you seeing

[jira] [Updated] (HDFS-7398) Reset cached thread-local FSEditLogOp's on every FSEditLog#logEdit

[ https://issues.apache.org/jira/browse/HDFS-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7398: Resolution: Fixed Fix Version/s: 2.7.0 Status: Resolved (was: Patch Available) I

[jira] [Updated] (HDFS-7398) Reset cached thread-local FSEditLogOp's on every FSEditLog#logEdit

[ https://issues.apache.org/jira/browse/HDFS-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7398: Hadoop Flags: Reviewed bq. Access to protected is the superset of the package scope according to the

[jira] [Commented] (HDFS-7396) Revisit synchronization in Namenode

[ https://issues.apache.org/jira/browse/HDFS-7396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212469#comment-14212469 ] Chris Nauroth commented on HDFS-7396: - bq. Whenever we experimented with improving

[jira] [Commented] (HDFS-7384) 'getfacl' command and 'getAclStatus' output should be in sync

[ https://issues.apache.org/jira/browse/HDFS-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212548#comment-14212548 ] Chris Nauroth commented on HDFS-7384: - Hi, [~vinayrpet]. The current behavior of

[jira] [Commented] (HDFS-7177) Add an option to include minimal ACL in getAclStatus return

[ https://issues.apache.org/jira/browse/HDFS-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212555#comment-14212555 ] Chris Nauroth commented on HDFS-7177: - Hi, [~zhz]. I just realized too late that

[jira] [Resolved] (HDFS-7177) Add an option to include minimal ACL in getAclStatus return

[ https://issues.apache.org/jira/browse/HDFS-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HDFS-7177. - Resolution: Duplicate Add an option to include minimal ACL in getAclStatus return

[jira] [Updated] (HDFS-6962) ACLs inheritance conflict with umaskmode

[ https://issues.apache.org/jira/browse/HDFS-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-6962: Target Version/s: 2.7.0 (was: 2.4.1) Hello, [~Alexandre LINTE]. Thank you for filing this issue.

[jira] [Commented] (HDFS-7384) 'getfacl' command and 'getAclStatus' output should be in sync

[ https://issues.apache.org/jira/browse/HDFS-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212734#comment-14212734 ] Chris Nauroth commented on HDFS-7384: - Yes, what you described makes sense. An older

[jira] [Resolved] (HDFS-6711) FSNamesystem#getAclStatus does not write to the audit log.

[ https://issues.apache.org/jira/browse/HDFS-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HDFS-6711. - Resolution: Duplicate FSNamesystem#getAclStatus does not write to the audit log.

[jira] [Commented] (HDFS-6711) FSNamesystem#getAclStatus does not write to the audit log.

[ https://issues.apache.org/jira/browse/HDFS-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212736#comment-14212736 ] Chris Nauroth commented on HDFS-6711: - This was fixed in HDFS-7218, so I'm resolving

[jira] [Resolved] (HDFS-3806) Assertion failed in TestStandbyCheckpoints.testBothNodesInStandbyState

[ https://issues.apache.org/jira/browse/HDFS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HDFS-3806. - Resolution: Duplicate I'm resolving this as duplicate of HDFS-3519. Assertion failed in

[jira] [Updated] (HDFS-7386) Replace check port number 1024 with shared isPrivilegedPort method

[ https://issues.apache.org/jira/browse/HDFS-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7386: Component/s: security datanode Target Version/s: 2.7.0 Hadoop

[jira] [Updated] (HDFS-7386) Replace check port number 1024 with shared isPrivilegedPort method

[ https://issues.apache.org/jira/browse/HDFS-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7386: Resolution: Fixed Fix Version/s: 2.7.0 Status: Resolved (was: Patch Available) I

[jira] [Resolved] (HDFS-3749) Disable check for jsvc on windows

[ https://issues.apache.org/jira/browse/HDFS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HDFS-3749. - Resolution: Won't Fix This is no longer required, because HDFS-2856 has been implemented,

[jira] [Commented] (HDFS-7384) 'getfacl' command and 'getAclStatus' output should be in sync

[ https://issues.apache.org/jira/browse/HDFS-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14213439#comment-14213439 ] Chris Nauroth commented on HDFS-7384: - I haven't reviewed the whole patch yet, but I

[jira] [Updated] (HDFS-7385) ThreadLocal used in FSEditLog class lead FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7385: Attachment: HDFS-7385.2.patch Hello, [~jiangyu1211]. Like others have already said, this is a great

[jira] [Updated] (HDFS-7385) ThreadLocal used in FSEditLog class lead FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7385: Status: Patch Available (was: Open) ThreadLocal used in FSEditLog class lead FSImage permission

[jira] [Updated] (HDFS-7385) ThreadLocal used in FSEditLog class lead FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7385: Due Date: 13/Nov/14 (was: 10/Nov/14) Priority: Blocker (was: Critical) General consensus is

[jira] [Updated] (HDFS-7385) ThreadLocal used in FSEditLog class lead FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7385: Hadoop Flags: Reviewed For {{TestCacheDirectives}}, it looks like we hit one of the build collision

[jira] [Updated] (HDFS-7385) ThreadLocal used in FSEditLog class causes FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7385: Summary: ThreadLocal used in FSEditLog class causes FSImage permission mess up (was: ThreadLocal

[jira] [Updated] (HDFS-7385) ThreadLocal used in FSEditLog class causes FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7385: Fix Version/s: 2.6.0 ThreadLocal used in FSEditLog class causes FSImage permission mess up

[jira] [Updated] (HDFS-7385) ThreadLocal used in FSEditLog class causes FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7385: Resolution: Fixed Status: Resolved (was: Patch Available) I committed this to trunk,

[jira] [Commented] (HDFS-7385) ThreadLocal used in FSEditLog class causes FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14211286#comment-14211286 ] Chris Nauroth commented on HDFS-7385: - I agree. The workaround makes sense. Thanks

[jira] [Commented] (HDFS-7385) ThreadLocal used in FSEditLog class causes FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14211505#comment-14211505 ] Chris Nauroth commented on HDFS-7385: - Hi, [~jira.shegalov]. Yes, I had the same

[jira] [Commented] (HDFS-7385) ThreadLocal used in FSEditLog class causes FSImage permission mess up

[ https://issues.apache.org/jira/browse/HDFS-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14211525#comment-14211525 ] Chris Nauroth commented on HDFS-7385: - On a side note, I have to wonder if the

[jira] [Commented] (HDFS-7386) Replace check port number 1024 with shared isPrivilegedPort method

[ https://issues.apache.org/jira/browse/HDFS-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208354#comment-14208354 ] Chris Nauroth commented on HDFS-7386: - Hi Yongjun. On further reflection, I think we

[jira] [Updated] (HDFS-7387) NFS may only do partial commit due to a race between COMMIT and write

[ https://issues.apache.org/jira/browse/HDFS-7387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7387: Fix Version/s: (was: 2.7.0) 2.6.0 I've merged this to branch-2.6 and

[jira] [Commented] (HDFS-7386) Replace check port number 1024 with shared isPrivilegedPort method

[ https://issues.apache.org/jira/browse/HDFS-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14209227#comment-14209227 ] Chris Nauroth commented on HDFS-7386: - Thanks for the patch, Yongjun. This looks good.

[jira] [Updated] (HDFS-7389) Named user ACL cannot stop the user from accessing the FS entity.

[ https://issues.apache.org/jira/browse/HDFS-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7389: Hadoop Flags: Reviewed Thank you for reporting this, [~chunjun.xiao]. [~vinayrpet], the patch looks

[jira] [Updated] (HDFS-7389) Named user ACL cannot stop the user from accessing the FS entity.

[ https://issues.apache.org/jira/browse/HDFS-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7389: Resolution: Fixed Fix Version/s: 2.7.0 Status: Resolved (was: Patch Available) I

[jira] [Commented] (HDFS-7328) TestTraceAdmin assumes Unix line endings.

[ https://issues.apache.org/jira/browse/HDFS-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205128#comment-14205128 ] Chris Nauroth commented on HDFS-7328: - No problem, [~cmccabe]. bq. It seems like Java

[jira] [Created] (HDFS-7382) DataNode in secure mode may throw NullPointerException if client connects before DataNode registers itself with NameNode.

Chris Nauroth created HDFS-7382: --- Summary: DataNode in secure mode may throw NullPointerException if client connects before DataNode registers itself with NameNode. Key: HDFS-7382 URL:

[jira] [Updated] (HDFS-7382) DataNode in secure mode may throw NullPointerException if client connects before DataNode registers itself with NameNode.

[ https://issues.apache.org/jira/browse/HDFS-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7382: Component/s: security DataNode in secure mode may throw NullPointerException if client connects

[jira] [Updated] (HDFS-7382) DataNode in secure mode may throw NullPointerException if client connects before DataNode registers itself with NameNode.

[ https://issues.apache.org/jira/browse/HDFS-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7382: Attachment: HDFS-7382.1.patch We don't really need to rely on NameNode registration. A DataNode

[jira] [Updated] (HDFS-7382) DataNode in secure mode may throw NullPointerException if client connects before DataNode registers itself with NameNode.

[ https://issues.apache.org/jira/browse/HDFS-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7382: Status: Patch Available (was: Open) DataNode in secure mode may throw NullPointerException if

[jira] [Updated] (HDFS-7382) DataNode in secure mode may throw NullPointerException if client connects before DataNode registers itself with NameNode.

[ https://issues.apache.org/jira/browse/HDFS-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7382: Attachment: HDFS-7382.2.patch Thank you for the code reviews, Nicholas and Yongjun. Yongjun, I'm

[jira] [Updated] (HDFS-7382) DataNode in secure mode may throw NullPointerException if client connects before DataNode registers itself with NameNode.

[ https://issues.apache.org/jira/browse/HDFS-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7382: Resolution: Fixed Fix Version/s: 2.6.0 Status: Resolved (was: Patch Available) I

[jira] [Updated] (HDFS-7383) DataNode.requestShortCircuitFdsForRead may throw NullPointerException

[ https://issues.apache.org/jira/browse/HDFS-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7383: Hadoop Flags: Reviewed +1 for the patch. The test failures look unrelated, and I verified that the

[jira] [Updated] (HDFS-7221) TestDNFencingWithReplication fails consistently

[ https://issues.apache.org/jira/browse/HDFS-7221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7221: Target Version/s: 2.6.0 (was: 2.7.0) Fix Version/s: (was: 2.7.0)

[jira] [Updated] (HDFS-7226) TestDNFencing.testQueueingWithAppend failed often in latest test

[ https://issues.apache.org/jira/browse/HDFS-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7226: Fix Version/s: (was: 2.7.0) 2.6.0 Thank you again for fixing this, Yongjun.

[jira] [Updated] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7359: Attachment: HDFS-7359.1.patch Here is a patch that fixes the bug by catching the error in

[jira] [Updated] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7359: Status: Patch Available (was: Open) NameNode in secured HA cluster fails to start if

[jira] [Updated] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7359: Attachment: HDFS-7359.2.patch Here is patch v2. We need one more change in {{ImageServlet}} to

[jira] [Commented] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14198839#comment-14198839 ] Chris Nauroth commented on HDFS-7359: - That's a good question. I believe we'll still

[jira] [Updated] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7359: Attachment: HDFS-7359.3.patch Here is patch v3 with the improved logging. I still retained logging

[jira] [Commented] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14199124#comment-14199124 ] Chris Nauroth commented on HDFS-7359: - The test failures are unrelated.

[jira] [Created] (HDFS-7361) TestCheckpoint#testStorageAlreadyLockedErrorMessage fails after change of log message related to locking violation.

Chris Nauroth created HDFS-7361: --- Summary: TestCheckpoint#testStorageAlreadyLockedErrorMessage fails after change of log message related to locking violation. Key: HDFS-7361 URL:

[jira] [Commented] (HDFS-7361) TestCheckpoint#testStorageAlreadyLockedErrorMessage fails after change of log message related to locking violation.

[ https://issues.apache.org/jira/browse/HDFS-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14199171#comment-14199171 ] Chris Nauroth commented on HDFS-7361: - Here is the output from a failed test run.

[jira] [Commented] (HDFS-7333) Improve log message in Storage.tryLock()

[ https://issues.apache.org/jira/browse/HDFS-7333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14199174#comment-14199174 ] Chris Nauroth commented on HDFS-7333: - This patch introduced a test failure in

[jira] [Commented] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14199176#comment-14199176 ] Chris Nauroth commented on HDFS-7359: - The {{TestCheckpoint}} failure was introduced in

[jira] [Updated] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7359: Hadoop Flags: Reviewed I think something confused the string parsing Jenkins does to search for

[jira] [Updated] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7359: Component/s: namenode NameNode in secured HA cluster fails to start if

[jira] [Updated] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

[ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7359: Resolution: Fixed Fix Version/s: 2.6.0 Status: Resolved (was: Patch Available) I

[jira] [Updated] (HDFS-7361) TestCheckpoint#testStorageAlreadyLockedErrorMessage fails after change of log message related to locking violation.

[ https://issues.apache.org/jira/browse/HDFS-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7361: Hadoop Flags: Reviewed +1 for the patch, pending Jenkins run. Thanks for the quick fix, [~shv].

[jira] [Created] (HDFS-7367) HDFS short-circuit read cannot negotiate shared memory slot and file descriptors when SASL is enabled on DataTransferProtocol.

Chris Nauroth created HDFS-7367: --- Summary: HDFS short-circuit read cannot negotiate shared memory slot and file descriptors when SASL is enabled on DataTransferProtocol. Key: HDFS-7367 URL:

[jira] [Updated] (HDFS-7367) HDFS short-circuit read cannot negotiate shared memory slot and file descriptors when SASL is enabled on DataTransferProtocol.

[ https://issues.apache.org/jira/browse/HDFS-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7367: Attachment: HDFS-7367.1.patch I'm attaching a patch with the simple fix. We just need to check if

[jira] [Commented] (HDFS-7367) HDFS short-circuit read cannot negotiate shared memory slot and file descriptors when SASL is enabled on DataTransferProtocol.

[ https://issues.apache.org/jira/browse/HDFS-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14199485#comment-14199485 ] Chris Nauroth commented on HDFS-7367: - I also meant to mention that this is exactly the

[jira] [Updated] (HDFS-7367) HDFS short-circuit read cannot negotiate shared memory slot and file descriptors when SASL is enabled on DataTransferProtocol.

[ https://issues.apache.org/jira/browse/HDFS-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7367: Status: Patch Available (was: Open) HDFS short-circuit read cannot negotiate shared memory slot

[jira] [Updated] (HDFS-7218) FSNamesystem ACL operations should write to audit log on failure

[ https://issues.apache.org/jira/browse/HDFS-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7218: Hadoop Flags: Reviewed +1 from me too. Thank you, Charles. FSNamesystem ACL operations should

[jira] [Updated] (HDFS-7355) TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure fails on Windows, because we cannot deny access to the file owner.

[ https://issues.apache.org/jira/browse/HDFS-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7355: Status: Patch Available (was: Open) TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure

[jira] [Updated] (HDFS-7355) TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure fails on Windows, because we cannot deny access to the file owner.

[ https://issues.apache.org/jira/browse/HDFS-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7355: Attachment: HDFS-7355.1.patch The attached patch skips the test.

[jira] [Created] (HDFS-7355) TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure fails on Windows, because we cannot deny access to the file owner.

Chris Nauroth created HDFS-7355: --- Summary: TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure fails on Windows, because we cannot deny access to the file owner. Key: HDFS-7355 URL:

[jira] [Commented] (HDFS-7355) TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure fails on Windows, because we cannot deny access to the file owner.

[ https://issues.apache.org/jira/browse/HDFS-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14196734#comment-14196734 ] Chris Nauroth commented on HDFS-7355: -

[jira] [Commented] (HDFS-7208) NN doesn't schedule replication when a DN storage fails

[ https://issues.apache.org/jira/browse/HDFS-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14196752#comment-14196752 ] Chris Nauroth commented on HDFS-7208: - The new test cannot work correctly on Windows.

[jira] [Commented] (HDFS-7355) TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure fails on Windows, because we cannot deny access to the file owner.

[ https://issues.apache.org/jira/browse/HDFS-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14197127#comment-14197127 ] Chris Nauroth commented on HDFS-7355: - Thank you for the reviews and the commit, Ming

[jira] [Created] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

Chris Nauroth created HDFS-7359: --- Summary: NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address. Key: HDFS-7359 URL:

[jira] [Updated] (HDFS-7328) TestTraceAdmin assumes Unix line endings.

[ https://issues.apache.org/jira/browse/HDFS-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7328: Attachment: HDFS-7328.1.patch Here is a test fix to use the correct platform line separator.

[jira] [Created] (HDFS-7328) TestTraceAdmin assumes Unix line endings.

Chris Nauroth created HDFS-7328: --- Summary: TestTraceAdmin assumes Unix line endings. Key: HDFS-7328 URL: https://issues.apache.org/jira/browse/HDFS-7328 Project: Hadoop HDFS Issue Type: Bug

[jira] [Updated] (HDFS-7328) TestTraceAdmin assumes Unix line endings.

[ https://issues.apache.org/jira/browse/HDFS-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7328: Status: Patch Available (was: Open) TestTraceAdmin assumes Unix line endings.

[jira] [Updated] (HDFS-7328) TestTraceAdmin assumes Unix line endings.

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

[jira] [Updated] (HDFS-7313) Support optional configuration of AES cipher suite on DataTransferProtocol.

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

[jira] [Updated] (HDFS-6606) Optimize HDFS Encrypted Transport performance

[ https://issues.apache.org/jira/browse/HDFS-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-6606: Release Note: HDFS now supports the option to configure AES encryption for block data transfer. AES

[jira] [Commented] (HDFS-7313) Support optional configuration of AES cipher suite on DataTransferProtocol.

[ https://issues.apache.org/jira/browse/HDFS-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14192311#comment-14192311 ] Chris Nauroth commented on HDFS-7313: - bq. I haven't looked into this at all yet, but

[jira] [Commented] (HDFS-7313) Support optional configuration of AES cipher suite on DataTransferProtocol.

[ https://issues.apache.org/jira/browse/HDFS-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14192332#comment-14192332 ] Chris Nauroth commented on HDFS-7313: - No problem! One more note: we actually cover

[jira] [Commented] (HDFS-6994) libhdfs3 - A native C/C++ HDFS client

[ https://issues.apache.org/jira/browse/HDFS-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190124#comment-14190124 ] Chris Nauroth commented on HDFS-6994: - bq. As in HDFS-573, the changes are scattered

[jira] [Updated] (HDFS-6385) Show when block deletion will start after NameNode startup in WebUI

[ https://issues.apache.org/jira/browse/HDFS-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-6385: Attachment: HDFS-6385.3.patch Patch v3 adds a detailed assertion message, so that I can get more

[jira] [Updated] (HDFS-6385) Show when block deletion will start after NameNode startup in WebUI

[ https://issues.apache.org/jira/browse/HDFS-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-6385: Attachment: HDFS-6385.4.patch My test was still comparing apples and oranges

[jira] [Commented] (HDFS-6994) libhdfs3 - A native C/C++ HDFS client

[ https://issues.apache.org/jira/browse/HDFS-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190847#comment-14190847 ] Chris Nauroth commented on HDFS-6994: - bq. In other word, should I wait until some

[jira] [Commented] (HDFS-7188) support build libhdfs3 on windows

[ https://issues.apache.org/jira/browse/HDFS-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190852#comment-14190852 ] Chris Nauroth commented on HDFS-7188: - bq. I've been working on porting libhdfs3 to

[jira] [Commented] (HDFS-6385) Show when block deletion will start after NameNode startup in WebUI

[ https://issues.apache.org/jira/browse/HDFS-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191036#comment-14191036 ] Chris Nauroth commented on HDFS-6385: - The failure in {{TestRetryCacheWithHA}} was

[jira] [Commented] (HDFS-6385) Show when block deletion will start after NameNode startup in WebUI

[ https://issues.apache.org/jira/browse/HDFS-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191037#comment-14191037 ] Chris Nauroth commented on HDFS-6385: - Disregard my last comment. I crossed replies.

[jira] [Created] (HDFS-7313) Support optional configuration of AES cipher suite on DataTransferProtocol.

Chris Nauroth created HDFS-7313: --- Summary: Support optional configuration of AES cipher suite on DataTransferProtocol. Key: HDFS-7313 URL: https://issues.apache.org/jira/browse/HDFS-7313 Project:

[jira] [Updated] (HDFS-7313) Support optional configuration of AES cipher suite on DataTransferProtocol.

[ https://issues.apache.org/jira/browse/HDFS-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7313: Status: Patch Available (was: Open) Support optional configuration of AES cipher suite on

<    6   7   8   9   10   11   12   13   14   15   >