[jira] [Commented] (HDFS-1490) TransferFSImage should timeout

[ https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442992#comment-13442992 ] Ravi Prakash commented on HDFS-1490: +1 lgtm TransferFSImage should

[jira] [Commented] (HDFS-3540) Further improvement on recovery mode and edit log toleration in branch-1

[ https://issues.apache.org/jira/browse/HDFS-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443002#comment-13443002 ] Tsz Wo (Nicholas), SZE commented on HDFS-3540: -- If the edit log is not

[jira] [Updated] (HDFS-1490) TransferFSImage should timeout

[ https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-1490: -- Status: Patch Available (was: Open) TransferFSImage should timeout

[jira] [Commented] (HDFS-1490) TransferFSImage should timeout

[ https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443034#comment-13443034 ] Hadoop QA commented on HDFS-1490: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-1490) TransferFSImage should timeout

[ https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443051#comment-13443051 ] Vinay commented on HDFS-1490: - {code} Call to equals() comparing different types in

[jira] [Assigned] (HDFS-3847) using NFS As a shared storage for NameNode HA , how to ensure that only one write

[ https://issues.apache.org/jira/browse/HDFS-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K reassigned HDFS-3847: --- Assignee: (was: Devaraj K) using NFS As a shared storage for NameNode HA , how to ensure

[jira] [Assigned] (HDFS-3847) using NFS As a shared storage for NameNode HA , how to ensure that only one write

[ https://issues.apache.org/jira/browse/HDFS-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K reassigned HDFS-3847: --- Assignee: Devaraj K using NFS As a shared storage for NameNode HA , how to ensure that only one

[jira] [Commented] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443056#comment-13443056 ] Suresh Srinivas commented on HDFS-3860: --- Jing, nice find. Submitting the patch.

[jira] [Commented] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443058#comment-13443058 ] Suresh Srinivas commented on HDFS-3860: --- BTW could you please also ensure that this

[jira] [Updated] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-3860: -- Status: Patch Available (was: Open) HeartbeatManager#Monitor may wrongly hold the

[jira] [Commented] (HDFS-3791) Backport HDFS-173 to Branch-1 : Recursively deleting a directory with millions of files makes NameNode unresponsive for other commands until the deletion completes

[ https://issues.apache.org/jira/browse/HDFS-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443075#comment-13443075 ] Suresh Srinivas commented on HDFS-3791: --- Uma sorry for the delay in reviewing this.

[jira] [Updated] (HDFS-3791) Backport HDFS-173 to Branch-1 : Recursively deleting a directory with millions of files makes NameNode unresponsive for other commands until the deletion completes

[ https://issues.apache.org/jira/browse/HDFS-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-3791: -- Attachment: HDFS-3791.patch Rebased the patch on latest branch-1 Backport

[jira] [Resolved] (HDFS-3791) Backport HDFS-173 to Branch-1 : Recursively deleting a directory with millions of files makes NameNode unresponsive for other commands until the deletion completes

[ https://issues.apache.org/jira/browse/HDFS-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-3791. --- Resolution: Fixed Fix Version/s: 1.2.0 Hadoop Flags: Reviewed I committed the

[jira] [Commented] (HDFS-3791) Backport HDFS-173 to Branch-1 : Recursively deleting a directory with millions of files makes NameNode unresponsive for other commands until the deletion completes

[ https://issues.apache.org/jira/browse/HDFS-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443103#comment-13443103 ] Uma Maheswara Rao G commented on HDFS-3791: --- Oh, I have just seen the comments.

[jira] [Commented] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443105#comment-13443105 ] Hadoop QA commented on HDFS-3860: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3837) Fix DataNode.recoverBlock findbugs warning

[ https://issues.apache.org/jira/browse/HDFS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443113#comment-13443113 ] Suresh Srinivas commented on HDFS-3837: --- Seems to me the findbugs is not fixed by the

[jira] [Commented] (HDFS-3856) TestHDFSServerPorts failure is causing surefire fork failure

[ https://issues.apache.org/jira/browse/HDFS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443123#comment-13443123 ] Hudson commented on HDFS-3856: -- Integrated in Hadoop-Hdfs-trunk #1148 (See

[jira] [Commented] (HDFS-3856) TestHDFSServerPorts failure is causing surefire fork failure

[ https://issues.apache.org/jira/browse/HDFS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443151#comment-13443151 ] Hudson commented on HDFS-3856: -- Integrated in Hadoop-Mapreduce-trunk #1179 (See

[jira] [Updated] (HDFS-3852) TestHftpDelegationToken is broken after HADOOP-8225

[ https://issues.apache.org/jira/browse/HDFS-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated HDFS-3852: -- Attachment: HDFS-3852.patch The test is attempting to insert two tokens with the same service. The

[jira] [Updated] (HDFS-3852) TestHftpDelegationToken is broken after HADOOP-8225

[ https://issues.apache.org/jira/browse/HDFS-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated HDFS-3852: -- Status: Patch Available (was: Open) TestHftpDelegationToken is broken after HADOOP-8225

[jira] [Commented] (HDFS-3852) TestHftpDelegationToken is broken after HADOOP-8225

[ https://issues.apache.org/jira/browse/HDFS-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443212#comment-13443212 ] Aaron T. Myers commented on HDFS-3852: -- Got it. Makes sense. Thanks for the

[jira] [Commented] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0

[ https://issues.apache.org/jira/browse/HDFS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443221#comment-13443221 ] Robert Joseph Evans commented on HDFS-3731: --- Any update on branch-0.23? Do you

[jira] [Updated] (HDFS-3837) Fix DataNode.recoverBlock findbugs warning

[ https://issues.apache.org/jira/browse/HDFS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-3837: -- Attachment: hdfs-3837.txt The findbugs warning seems bogus - This method calls equals(Object) on two

[jira] [Commented] (HDFS-3791) Backport HDFS-173 to Branch-1 : Recursively deleting a directory with millions of files makes NameNode unresponsive for other commands until the deletion completes

[ https://issues.apache.org/jira/browse/HDFS-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443245#comment-13443245 ] Ted Yu commented on HDFS-3791: -- Currently small deletion is determined by the constant

[jira] [Commented] (HDFS-3852) TestHftpDelegationToken is broken after HADOOP-8225

[ https://issues.apache.org/jira/browse/HDFS-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443264#comment-13443264 ] Hadoop QA commented on HDFS-3852: - -1 overall. Here are the results of testing the latest

[jira] [Created] (HDFS-3861) Deadlock in DFSClient

Kihwal Lee created HDFS-3861: Summary: Deadlock in DFSClient Key: HDFS-3861 URL: https://issues.apache.org/jira/browse/HDFS-3861 Project: Hadoop HDFS Issue Type: Bug Affects Versions:

[jira] [Commented] (HDFS-3861) Deadlock in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443269#comment-13443269 ] Kihwal Lee commented on HDFS-3861: -- DFSClient#getLeaseRenewer() doesn't have to be

[jira] [Commented] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443271#comment-13443271 ] Aaron T. Myers commented on HDFS-3860: -- Oof, good catch, Jing. Fortunately this case

[jira] [Updated] (HDFS-3861) Deadlock in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-3861: - Attachment: hdfs-3861.patch.txt Deadlock in DFSClient - Key:

[jira] [Updated] (HDFS-3861) Deadlock in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-3861: - Status: Patch Available (was: Open) Deadlock in DFSClient -

[jira] [Updated] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

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

[jira] [Commented] (HDFS-3837) Fix DataNode.recoverBlock findbugs warning

[ https://issues.apache.org/jira/browse/HDFS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443286#comment-13443286 ] Suresh Srinivas commented on HDFS-3837: --- If this is a findbugs issue, why not just

[jira] [Commented] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443289#comment-13443289 ] Suresh Srinivas commented on HDFS-3860: --- Thanks Aaron for committing the patch. bq.

[jira] [Commented] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443292#comment-13443292 ] Jing Zhao commented on HDFS-3860: - I just checked all the invocation of

[jira] [Commented] (HDFS-3791) Backport HDFS-173 to Branch-1 : Recursively deleting a directory with millions of files makes NameNode unresponsive for other commands until the deletion completes

[ https://issues.apache.org/jira/browse/HDFS-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443296#comment-13443296 ] Suresh Srinivas commented on HDFS-3791: --- when I added this in trunk, I was not sure

[jira] [Assigned] (HDFS-3861) Deadlock in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee reassigned HDFS-3861: Assignee: Kihwal Lee Deadlock in DFSClient - Key:

[jira] [Updated] (HDFS-2815) Namenode is not coming out of safemode when we perform ( NN crash + restart ) . Also FSCK report shows blocks missed.

[ https://issues.apache.org/jira/browse/HDFS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-2815: -- Attachment: HDFS-2815-branch-1.patch Namenode is not coming out of safemode when

[jira] [Updated] (HDFS-3373) FileContext HDFS implementation can leak socket caches

[ https://issues.apache.org/jira/browse/HDFS-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-3373: -- Status: Open (was: Patch Available) FileContext HDFS implementation can leak socket caches

[jira] [Updated] (HDFS-3373) FileContext HDFS implementation can leak socket caches

[ https://issues.apache.org/jira/browse/HDFS-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-3373: -- Attachment: HDFS-3373.trunk.patch.1 TestConnCache failure is related to this JIRA. I had moved

[jira] [Updated] (HDFS-3373) FileContext HDFS implementation can leak socket caches

[ https://issues.apache.org/jira/browse/HDFS-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-3373: -- Status: Patch Available (was: Open) FileContext HDFS implementation can leak socket caches

[jira] [Updated] (HDFS-3004) Implement Recovery Mode

[ https://issues.apache.org/jira/browse/HDFS-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-3004: --- Attachment: recovery-mode.pdf Here is an updated Recovery Mode design document.

[jira] [Commented] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443338#comment-13443338 ] Hudson commented on HDFS-3860: -- Integrated in Hadoop-Mapreduce-trunk-Commit #2680 (See

[jira] [Commented] (HDFS-3861) Deadlock in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443351#comment-13443351 ] Hadoop QA commented on HDFS-3861: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443353#comment-13443353 ] Hudson commented on HDFS-3860: -- Integrated in Hadoop-Common-trunk-Commit #2651 (See

[jira] [Commented] (HDFS-3860) HeartbeatManager#Monitor may wrongly hold the writelock of namesystem

[ https://issues.apache.org/jira/browse/HDFS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443367#comment-13443367 ] Hudson commented on HDFS-3860: -- Integrated in Hadoop-Hdfs-trunk-Commit #2715 (See

[jira] [Commented] (HDFS-3540) Further improvement on recovery mode and edit log toleration in branch-1

[ https://issues.apache.org/jira/browse/HDFS-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443375#comment-13443375 ] Colin Patrick McCabe commented on HDFS-3540: Hi Nicholas, Your summary seems

[jira] [Commented] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0

[ https://issues.apache.org/jira/browse/HDFS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443377#comment-13443377 ] Colin Patrick McCabe commented on HDFS-3731: bq. Any update on branch-0.23? Do

[jira] [Commented] (HDFS-3837) Fix DataNode.recoverBlock findbugs warning

[ https://issues.apache.org/jira/browse/HDFS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443387#comment-13443387 ] Hadoop QA commented on HDFS-3837: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2815) Namenode is not coming out of safemode when we perform ( NN crash + restart ) . Also FSCK report shows blocks missed.

[ https://issues.apache.org/jira/browse/HDFS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443394#comment-13443394 ] Hadoop QA commented on HDFS-2815: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3861) Deadlock in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443401#comment-13443401 ] Kihwal Lee commented on HDFS-3861: -- - The test failures are not related to this patch. -

[jira] [Updated] (HDFS-3849) When re-loading the FSImage, we should clear the existing genStamp and leases.

[ https://issues.apache.org/jira/browse/HDFS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-3849: --- Attachment: HDFS-3849.003.patch * don't set DT config When

[jira] [Commented] (HDFS-3849) When re-loading the FSImage, we should clear the existing genStamp and leases.

[ https://issues.apache.org/jira/browse/HDFS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443445#comment-13443445 ] Aaron T. Myers commented on HDFS-3849: -- +1 pending Jenkins. When

[jira] [Commented] (HDFS-3861) Deadlock in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443463#comment-13443463 ] Colin Patrick McCabe commented on HDFS-3861: Looks good to me.

[jira] [Commented] (HDFS-3859) QJM: implement md5sum verification

[ https://issues.apache.org/jira/browse/HDFS-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443476#comment-13443476 ] Steve Loughran commented on HDFS-3859: -- Isn't MD5 overkill? Can't a good CRC (like TCP

[jira] [Commented] (HDFS-3859) QJM: implement md5sum verification

[ https://issues.apache.org/jira/browse/HDFS-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443483#comment-13443483 ] Todd Lipcon commented on HDFS-3859: --- Sure, it's overkill, but it's not that expensive and

[jira] [Created] (HDFS-3862) QJM: don't require a fencer to be configured if shared storage has built-in single-writer semantics

Todd Lipcon created HDFS-3862: - Summary: QJM: don't require a fencer to be configured if shared storage has built-in single-writer semantics Key: HDFS-3862 URL: https://issues.apache.org/jira/browse/HDFS-3862

[jira] [Commented] (HDFS-3862) QJM: don't require a fencer to be configured if shared storage has built-in single-writer semantics

[ https://issues.apache.org/jira/browse/HDFS-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443518#comment-13443518 ] Todd Lipcon commented on HDFS-3862: --- I think this might be the case for BookKeeper as

[jira] [Commented] (HDFS-3373) FileContext HDFS implementation can leak socket caches

[ https://issues.apache.org/jira/browse/HDFS-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443524#comment-13443524 ] Hadoop QA commented on HDFS-3373: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-1490) TransferFSImage should timeout

[ https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443526#comment-13443526 ] Todd Lipcon commented on HDFS-1490: --- - I dont like reusing the ipc ping interval for this

[jira] [Commented] (HDFS-3849) When re-loading the FSImage, we should clear the existing genStamp and leases.

[ https://issues.apache.org/jira/browse/HDFS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443541#comment-13443541 ] Hadoop QA commented on HDFS-3849: - -1 overall. Here are the results of testing the latest

[jira] [Created] (HDFS-3863) QJM: track last committed txid

Todd Lipcon created HDFS-3863: - Summary: QJM: track last committed txid Key: HDFS-3863 URL: https://issues.apache.org/jira/browse/HDFS-3863 Project: Hadoop HDFS Issue Type: Sub-task

[jira] [Commented] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0

[ https://issues.apache.org/jira/browse/HDFS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443551#comment-13443551 ] Robert Joseph Evans commented on HDFS-3731: --- Do you have a list of ones you know

[jira] [Commented] (HDFS-3863) QJM: track last committed txid

[ https://issues.apache.org/jira/browse/HDFS-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443556#comment-13443556 ] Todd Lipcon commented on HDFS-3863: --- The design here is pretty simple, given the way our

[jira] [Commented] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0

[ https://issues.apache.org/jira/browse/HDFS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443577#comment-13443577 ] Colin Patrick McCabe commented on HDFS-3731: bq. Do you have a list of ones you

[jira] [Created] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

Aaron T. Myers created HDFS-3864: Summary: NN does not update internal file mtime for OP_CLOSE when reading from the edit log Key: HDFS-3864 URL: https://issues.apache.org/jira/browse/HDFS-3864

[jira] [Commented] (HDFS-3733) Audit logs should include WebHDFS access

[ https://issues.apache.org/jira/browse/HDFS-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443584#comment-13443584 ] Andy Isaacson commented on HDFS-3733: - OK, backing up -- I think my addition of

[jira] [Updated] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

[ https://issues.apache.org/jira/browse/HDFS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-3864: - Status: Patch Available (was: Open) NN does not update internal file mtime for OP_CLOSE

[jira] [Updated] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

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

[jira] [Created] (HDFS-3865) TestDistCp is @ignored

Colin Patrick McCabe created HDFS-3865: -- Summary: TestDistCp is @ignored Key: HDFS-3865 URL: https://issues.apache.org/jira/browse/HDFS-3865 Project: Hadoop HDFS Issue Type: Test

[jira] [Updated] (HDFS-3849) When re-loading the FSImage, we should clear the existing genStamp and leases.

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

[jira] [Updated] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

[ https://issues.apache.org/jira/browse/HDFS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-3864: - Attachment: HDFS-3864.patch Thanks a lot for the quick review, Todd. Here's an updated patch

[jira] [Commented] (HDFS-3849) When re-loading the FSImage, we should clear the existing genStamp and leases.

[ https://issues.apache.org/jira/browse/HDFS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443598#comment-13443598 ] Hudson commented on HDFS-3849: -- Integrated in Hadoop-Hdfs-trunk-Commit #2716 (See

[jira] [Comment Edited] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

[ https://issues.apache.org/jira/browse/HDFS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443586#comment-13443586 ] Aaron T. Myers edited comment on HDFS-3864 at 8/29/12 9:21 AM:

[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-tabpanelfocusedCommentId=13443610#comment-13443610 ] Aaron T. Myers commented on HDFS-2264: -- Hey Jitendra, sorry for forgetting about this

[jira] [Comment Edited] (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-tabpanelfocusedCommentId=13443610#comment-13443610 ] Aaron T. Myers edited comment on HDFS-2264 at 8/29/12 9:45 AM:

[jira] [Commented] (HDFS-3849) When re-loading the FSImage, we should clear the existing genStamp and leases.

[ https://issues.apache.org/jira/browse/HDFS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443624#comment-13443624 ] Hudson commented on HDFS-3849: -- Integrated in Hadoop-Mapreduce-trunk-Commit #2682 (See

[jira] [Updated] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HDFS-3466: Attachment: hdfs-3466-b1-2.patch Here's a patch that incorporates Eli's feedback.

[jira] [Updated] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HDFS-3466: Attachment: hdfs-3466-trunk.patch The SPNEGO filter for the NameNode should come out of the

[jira] [Updated] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HDFS-3466: Attachment: (was: hdfs-3466-trunk.patch) The SPNEGO filter for the NameNode should come

[jira] [Updated] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HDFS-3466: Attachment: (was: hdfs-3466-trunk.patch) The SPNEGO filter for the NameNode should come

[jira] [Updated] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HDFS-3466: Attachment: hdfs-3466-trunk-2.patch The SPNEGO filter for the NameNode should come out of the

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443645#comment-13443645 ] Hadoop QA commented on HDFS-3466: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443654#comment-13443654 ] Hadoop QA commented on HDFS-3466: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

[ https://issues.apache.org/jira/browse/HDFS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443657#comment-13443657 ] Hadoop QA commented on HDFS-3864: - -1 overall. Here are the results of testing the latest

[jira] [Updated] (HDFS-3855) Replace hardcoded strings with the already defined config keys in DataNode.java

[ https://issues.apache.org/jira/browse/HDFS-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Li updated HDFS-3855: - Description: Replace hardcoded strings with the already defined config keys in DataNode.java

[jira] [Commented] (HDFS-3135) Build a war file for HttpFS instead of packaging the server (tomcat) along with the application.

[ https://issues.apache.org/jira/browse/HDFS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443710#comment-13443710 ] Ryan Hennig commented on HDFS-3135: --- I'm troubleshooting a broken build that fails on the

[jira] [Commented] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

[ https://issues.apache.org/jira/browse/HDFS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443712#comment-13443712 ] Hadoop QA commented on HDFS-3864: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

[ https://issues.apache.org/jira/browse/HDFS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443715#comment-13443715 ] Aaron T. Myers commented on HDFS-3864: -- The findbugs warning is unrelated and I'm

[jira] [Updated] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

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

[jira] [Commented] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

[ https://issues.apache.org/jira/browse/HDFS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443737#comment-13443737 ] Hudson commented on HDFS-3864: -- Integrated in Hadoop-Hdfs-trunk-Commit #2717 (See

[jira] [Commented] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

[ https://issues.apache.org/jira/browse/HDFS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443738#comment-13443738 ] Hudson commented on HDFS-3864: -- Integrated in Hadoop-Common-trunk-Commit #2654 (See

[jira] [Commented] (HDFS-3864) NN does not update internal file mtime for OP_CLOSE when reading from the edit log

[ https://issues.apache.org/jira/browse/HDFS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443752#comment-13443752 ] Hudson commented on HDFS-3864: -- Integrated in Hadoop-Mapreduce-trunk-Commit #2683 (See

[jira] [Commented] (HDFS-1490) TransferFSImage should timeout

[ https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443791#comment-13443791 ] Vinay commented on HDFS-1490: - {quote}Why not introduce a new config which defaults to

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443810#comment-13443810 ] Eli Collins commented on HDFS-3466: --- Hey Owen, I think you meant to remove the 2nd

[jira] [Commented] (HDFS-3865) TestDistCp is @ignored

[ https://issues.apache.org/jira/browse/HDFS-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443812#comment-13443812 ] Eli Collins commented on HDFS-3865: --- Looks like some of the tests are commented out as

[jira] [Resolved] (HDFS-282) Serialize ipcPort in DatanodeID instead of DatanodeRegistration and DatanodeInfo

[ https://issues.apache.org/jira/browse/HDFS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins resolved HDFS-282. -- Resolution: Not A Problem No longer an issue now that the writable methods have been removed.

[jira] [Commented] (HDFS-3837) Fix DataNode.recoverBlock findbugs warning

[ https://issues.apache.org/jira/browse/HDFS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443827#comment-13443827 ] Eli Collins commented on HDFS-3837: --- I investigated some more and confirmed findbugs

[jira] [Updated] (HDFS-3837) Fix DataNode.recoverBlock findbugs warning

[ https://issues.apache.org/jira/browse/HDFS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-3837: -- Attachment: hdfs-3837.txt Updated patch attached. Fix DataNode.recoverBlock findbugs