[jira] Updated: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-877: - Status: Open (was: Patch Available) > Client-driven block verification not functioning > -

[jira] Updated: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-877: - Attachment: hdfs-877.txt New patch addresses findbugs warning (isLastPacket member is now unused) > Client

[jira] Updated: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-877: - Status: Patch Available (was: Open) > Client-driven block verification not functioning > -

[jira] Commented: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797955#action_12797955 ] Hadoop QA commented on HDFS-877: -1 overall. Here are the results of testing the latest atta

[jira] Commented: (HDFS-145) FSNameSystem#addStoredBlock does not handle inconsistent block length correctly

[ https://issues.apache.org/jira/browse/HDFS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797956#action_12797956 ] dhruba borthakur commented on HDFS-145: --- is this a code cleanup issue then? > FSNameSy

[jira] Commented: (HDFS-151) Not all of DfsClient's operations check the FS is open before calling the remote system

[ https://issues.apache.org/jira/browse/HDFS-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798044#action_12798044 ] Steve Loughran commented on HDFS-151: - This should be easy to test > Not all of DfsClien

[jira] Commented: (HDFS-42) NetUtils.createSocketAddr NPEs if dfs.datanode.ipc.address is not set for a data node

[ https://issues.apache.org/jira/browse/HDFS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798046#action_12798046 ] Steve Loughran commented on HDFS-42: Reviewing this, I will go with the IOE unless anyone

[jira] Work started: (HDFS-165) NPE in datanode.handshake()

[ https://issues.apache.org/jira/browse/HDFS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-165 started by Steve Loughran. > NPE in datanode.handshake() > --- > > Key: HDFS-165 > URL: https://iss

[jira] Assigned: (HDFS-165) NPE in datanode.handshake()

[ https://issues.apache.org/jira/browse/HDFS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran reassigned HDFS-165: --- Assignee: Steve Loughran > NPE in datanode.handshake() > --- > >

[jira] Updated: (HDFS-165) NPE in datanode.handshake()

[ https://issues.apache.org/jira/browse/HDFS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-165: Fix Version/s: 0.22.0 Affects Version/s: 0.20.1 Status: Patch Available (was:

[jira] Updated: (HDFS-165) NPE in datanode.handshake()

[ https://issues.apache.org/jira/browse/HDFS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-165: Attachment: HDFS-165.patch Patch checks for shouldRun flag and throws an IOE if set while waiting for

[jira] Created: (HDFS-882) Datanode could log what hostname and ports its listening on on startup

Datanode could log what hostname and ports its listening on on startup -- Key: HDFS-882 URL: https://issues.apache.org/jira/browse/HDFS-882 Project: Hadoop HDFS Issue Type:

[jira] Work started: (HDFS-882) Datanode could log what hostname and ports its listening on on startup

[ https://issues.apache.org/jira/browse/HDFS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-882 started by Steve Loughran. > Datanode could log what hostname and ports its listening on on startup > -

[jira] Updated: (HDFS-882) Datanode could log what hostname and ports its listening on on startup

[ https://issues.apache.org/jira/browse/HDFS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-882: Status: Patch Available (was: In Progress) > Datanode could log what hostname and ports its listenin

[jira] Updated: (HDFS-882) Datanode could log what hostname and ports its listening on on startup

[ https://issues.apache.org/jira/browse/HDFS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-882: Attachment: HDFS-882.patch Two extra logs at debug level, no tests > Datanode could log what hostnam

[jira] Work started: (HDFS-883) Datanode shutdown should log problems with Storage.unlockAll()

[ https://issues.apache.org/jira/browse/HDFS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-883 started by Steve Loughran. > Datanode shutdown should log problems with Storage.unlockAll() > -

[jira] Created: (HDFS-883) Datanode shutdown should log problems with Storage.unlockAll()

Datanode shutdown should log problems with Storage.unlockAll() -- Key: HDFS-883 URL: https://issues.apache.org/jira/browse/HDFS-883 Project: Hadoop HDFS Issue Type: Improvement

[jira] Updated: (HDFS-883) Datanode shutdown should log problems with Storage.unlockAll()

[ https://issues.apache.org/jira/browse/HDFS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-883: Status: Patch Available (was: In Progress) > Datanode shutdown should log problems with Storage.unlo

[jira] Updated: (HDFS-883) Datanode shutdown should log problems with Storage.unlockAll()

[ https://issues.apache.org/jira/browse/HDFS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-883: Attachment: HDFS-883.patch Patch logs at warn level. No tests, not unless someone starts simulating

[jira] Created: (HDFS-884) DataNode makeInstance should report the directory list when failing to start up

DataNode makeInstance should report the directory list when failing to start up --- Key: HDFS-884 URL: https://issues.apache.org/jira/browse/HDFS-884 Project: Hadoop HDFS

[jira] Updated: (HDFS-884) DataNode makeInstance should report the directory list when failing to start up

[ https://issues.apache.org/jira/browse/HDFS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-884: Attachment: HDFS-884.patch Patch changes logging, prints exception stack traces on failure if you wan

[jira] Updated: (HDFS-884) DataNode makeInstance should report the directory list when failing to start up

[ https://issues.apache.org/jira/browse/HDFS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-884: Fix Version/s: 0.22.0 Status: Patch Available (was: Open) > DataNode makeInstance should

[jira] Created: (HDFS-885) Datanode toString() NPEs on null dnRegistration

Datanode toString() NPEs on null dnRegistration --- Key: HDFS-885 URL: https://issues.apache.org/jira/browse/HDFS-885 Project: Hadoop HDFS Issue Type: Improvement Components: data-node

[jira] Updated: (HDFS-885) Datanode toString() NPEs on null dnRegistration

[ https://issues.apache.org/jira/browse/HDFS-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-885: Status: Patch Available (was: Open) > Datanode toString() NPEs on null dnRegistration >

[jira] Updated: (HDFS-885) Datanode toString() NPEs on null dnRegistration

[ https://issues.apache.org/jira/browse/HDFS-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-885: Attachment: HDFS-885.patch Patch to {{toString()}}. No test. You'd need to create a datanode without

[jira] Commented: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798131#action_12798131 ] Suresh Srinivas commented on HDFS-877: -- TestFsck also times out waiting for client to re

[jira] Commented: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798139#action_12798139 ] Suresh Srinivas commented on HDFS-877: -- Ignore my previous comments. The problem in Test

[jira] Commented: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798146#action_12798146 ] Hairong Kuang commented on HDFS-877: Good catch, Todd! Is it possible that pos + bytesToR

[jira] Updated: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-877: - Status: Open (was: Patch Available) > Client-driven block verification not functioning > -

[jira] Commented: (HDFS-882) Datanode could log what hostname and ports its listening on on startup

[ https://issues.apache.org/jira/browse/HDFS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798176#action_12798176 ] Hadoop QA commented on HDFS-882: -1 overall. Here are the results of testing the latest atta

[jira] Commented: (HDFS-885) Datanode toString() NPEs on null dnRegistration

[ https://issues.apache.org/jira/browse/HDFS-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798182#action_12798182 ] Konstantin Boudnik commented on HDFS-885: - +1 looks good > Datanode toString() NPEs

[jira] Updated: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-877: - Status: Patch Available (was: Open) > Client-driven block verification not functioning > -

[jira] Updated: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-877: - Attachment: hdfs-877.txt bq. Is it possible that pos + bytesToRead > totalBytesToRead in case that the las

[jira] Commented: (HDFS-165) NPE in datanode.handshake()

[ https://issues.apache.org/jira/browse/HDFS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798200#action_12798200 ] Hadoop QA commented on HDFS-165: -1 overall. Here are the results of testing the latest atta

[jira] Commented: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798212#action_12798212 ] Hairong Kuang commented on HDFS-877: The change looks good to me. > I think we should al

[jira] Commented: (HDFS-878) FileStatus should have a field "isUnderConstruction"

[ https://issues.apache.org/jira/browse/HDFS-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798215#action_12798215 ] Zheng Shao commented on HDFS-878: - Instead of changing FileStatus which is incompatible, we c

[jira] Commented: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798222#action_12798222 ] Todd Lipcon commented on HDFS-877: -- bq. Anyway we need unit tests to get this fix committed

[jira] Created: (HDFS-886) TestHDFSTrash fails on Windows

TestHDFSTrash fails on Windows -- Key: HDFS-886 URL: https://issues.apache.org/jira/browse/HDFS-886 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.2 Reporter: Konstantin Shvachko

[jira] Commented: (HDFS-879) FileStatus should have the visible length of the file

[ https://issues.apache.org/jira/browse/HDFS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798225#action_12798225 ] Zheng Shao commented on HDFS-879: - I think cost won't be a big concern: As commented in HDFS

[jira] Commented: (HDFS-879) FileStatus should have the visible length of the file

[ https://issues.apache.org/jira/browse/HDFS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798227#action_12798227 ] Zheng Shao commented on HDFS-879: - do it in 2 ways: 1. Only do it for files under constructi

[jira] Commented: (HDFS-784) TestFsck times out on branch 0.20.1

[ https://issues.apache.org/jira/browse/HDFS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798232#action_12798232 ] Suresh Srinivas commented on HDFS-784: -- Patch in HDFS-127 resets DFSInputStream.failures

[jira] Reopened: (HDFS-127) DFSClient block read failures cause open DFSInputStream to become unusable

[ https://issues.apache.org/jira/browse/HDFS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE reopened HDFS-127: - Unfortunately, the 0.20 patch causes TestFsck failing; see [Suresh's comment|https://i

[jira] Commented: (HDFS-883) Datanode shutdown should log problems with Storage.unlockAll()

[ https://issues.apache.org/jira/browse/HDFS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798236#action_12798236 ] Hadoop QA commented on HDFS-883: -1 overall. Here are the results of testing the latest atta

[jira] Commented: (HDFS-879) FileStatus should have the visible length of the file

[ https://issues.apache.org/jira/browse/HDFS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798247#action_12798247 ] Hairong Kuang commented on HDFS-879: > Data Node heartbeat the size. You meant heatbeat t

[jira] Commented: (HDFS-127) DFSClient block read failures cause open DFSInputStream to become unusable

[ https://issues.apache.org/jira/browse/HDFS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798246#action_12798246 ] Tsz Wo (Nicholas), SZE commented on HDFS-127: - Checked 0.21 and 0.22, the problem

[jira] Resolved: (HDFS-127) DFSClient block read failures cause open DFSInputStream to become unusable

[ https://issues.apache.org/jira/browse/HDFS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-127. - Resolution: Fixed Fix Version/s: (was: 0.20.2) I have reverted the patch

[jira] Resolved: (HDFS-784) TestFsck times out on branch 0.20.1

[ https://issues.apache.org/jira/browse/HDFS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-784. - Resolution: Invalid After reverting HDSF-127 from 0.20, this issue becomes invalid.

[jira] Created: (HDFS-887) TestHDFSServerPorts fails on Windows

TestHDFSServerPorts fails on Windows Key: HDFS-887 URL: https://issues.apache.org/jira/browse/HDFS-887 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.22.0 Reporter: Konstantin Sh

[jira] Updated: (HDFS-887) TestHDFSServerPorts fails on Windows

[ https://issues.apache.org/jira/browse/HDFS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-887: - Component/s: test name-node > TestHDFSServerPorts fails on Windows > -

[jira] Updated: (HDFS-886) TestHDFSTrash fails on Windows

[ https://issues.apache.org/jira/browse/HDFS-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-886: - Component/s: test > TestHDFSTrash fails on Windows > -- > >

[jira] Created: (HDFS-888) TestModTime fails intermittently

TestModTime fails intermittently Key: HDFS-888 URL: https://issues.apache.org/jira/browse/HDFS-888 Project: Hadoop HDFS Issue Type: Bug Components: name-node, test Affects Versions: 0.22.0

[jira] Updated: (HDFS-873) DataNode directories as URIs

[ https://issues.apache.org/jira/browse/HDFS-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-873: - Attachment: dataDirURI.patch With this patch data-node directories are specified as URIs.

[jira] Updated: (HDFS-873) DataNode directories as URIs

[ https://issues.apache.org/jira/browse/HDFS-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-873: - Status: Patch Available (was: Open) > DataNode directories as URIs > -

[jira] Updated: (HDFS-816) TestLargeDirectoryDelete fails

[ https://issues.apache.org/jira/browse/HDFS-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-816: - Summary: TestLargeDirectoryDelete fails (was: TestLargeDirectoryDelete fails on windows)

[jira] Commented: (HDFS-885) Datanode toString() NPEs on null dnRegistration

[ https://issues.apache.org/jira/browse/HDFS-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798276#action_12798276 ] Hadoop QA commented on HDFS-885: -1 overall. Here are the results of testing the latest atta

[jira] Commented: (HDFS-880) TestNNLeaseRecovery fails on windows

[ https://issues.apache.org/jira/browse/HDFS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798282#action_12798282 ] Konstantin Shvachko commented on HDFS-880: -- I ran the test. It worked on my windows

[jira] Commented: (HDFS-878) FileStatus should have a field "isUnderConstruction"

[ https://issues.apache.org/jira/browse/HDFS-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798284#action_12798284 ] dhruba borthakur commented on HDFS-878: --- I agree with Eli. We should not change FileSta

[jira] Commented: (HDFS-884) DataNode makeInstance should report the directory list when failing to start up

[ https://issues.apache.org/jira/browse/HDFS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798286#action_12798286 ] Hadoop QA commented on HDFS-884: -1 overall. Here are the results of testing the latest atta

[jira] Updated: (HDFS-685) Use the user-to-groups mapping service in the NameNode

[ https://issues.apache.org/jira/browse/HDFS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-685: -- Attachment: MR-1083-0_20.2.patch Combined patch for HADOOP-4656, HDFS-685 and MAPREDUCE-1

[jira] Updated: (HDFS-768) HDFS Contrib project ivy dependencies are not included in binary target

[ https://issues.apache.org/jira/browse/HDFS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball updated HDFS-768: --- Attachment: HDFS-768.2.patch Here's a patch that uses the new approach to package contribs in HDFS. Th

[jira] Updated: (HDFS-768) HDFS Contrib project ivy dependencies are not included in binary target

[ https://issues.apache.org/jira/browse/HDFS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball updated HDFS-768: --- Status: Patch Available (was: Open) > HDFS Contrib project ivy dependencies are not included in binary

[jira] Commented: (HDFS-877) Client-driven block verification not functioning

[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798300#action_12798300 ] Hadoop QA commented on HDFS-877: -1 overall. Here are the results of testing the latest atta

[jira] Commented: (HDFS-873) DataNode directories as URIs

[ https://issues.apache.org/jira/browse/HDFS-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798306#action_12798306 ] Hadoop QA commented on HDFS-873: -1 overall. Here are the results of testing the latest atta

[jira] Commented: (HDFS-768) HDFS Contrib project ivy dependencies are not included in binary target

[ https://issues.apache.org/jira/browse/HDFS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798310#action_12798310 ] Hadoop QA commented on HDFS-768: -1 overall. Here are the results of testing the latest atta