[jira] [Updated] (HDFS-2538) option to disable fsck dots

[ https://issues.apache.org/jira/browse/HDFS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated HDFS-2538: Release Note: fsck does not print out dots for progress reporting by default. To print out dots,

[jira] [Commented] (HDFS-5624) Add HDFS tests for ACLs in combination with viewfs.

[ https://issues.apache.org/jira/browse/HDFS-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064789#comment-14064789 ] Hudson commented on HDFS-5624: -- FAILURE: Integrated in Hadoop-Yarn-trunk #615 (See

[jira] [Commented] (HDFS-6689) NFS doesn't return correct lookup access for directories

[ https://issues.apache.org/jira/browse/HDFS-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064788#comment-14064788 ] Hudson commented on HDFS-6689: -- FAILURE: Integrated in Hadoop-Yarn-trunk #615 (See

[jira] [Commented] (HDFS-6690) Deduplicate xattr names in memory

[ https://issues.apache.org/jira/browse/HDFS-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064799#comment-14064799 ] Hudson commented on HDFS-6690: -- FAILURE: Integrated in Hadoop-Yarn-trunk #615 (See

[jira] [Commented] (HDFS-2538) option to disable fsck dots

[ https://issues.apache.org/jira/browse/HDFS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064798#comment-14064798 ] Hudson commented on HDFS-2538: -- FAILURE: Integrated in Hadoop-Yarn-trunk #615 (See

[jira] [Created] (HDFS-6699) Secure Windows DFS read when client co-located on nodes with data (short-circuit reads)

Remus Rusanu created HDFS-6699: -- Summary: Secure Windows DFS read when client co-located on nodes with data (short-circuit reads) Key: HDFS-6699 URL: https://issues.apache.org/jira/browse/HDFS-6699

[jira] [Updated] (HDFS-6699) Secure Windows DFS read when client co-located on nodes with data (short-circuit reads)

[ https://issues.apache.org/jira/browse/HDFS-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated HDFS-6699: --- Description: HDFS-347 Introduced secure short-circuit HDFS reads based on linux domain sockets.

[jira] [Updated] (HDFS-6680) BlockPlacementPolicyDefault does not choose favored nodes correctly

[ https://issues.apache.org/jira/browse/HDFS-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-6680: -- Attachment: h6680_20140716.patch h6680_20140716.patch: fixes another bug in the loop

[jira] [Updated] (HDFS-6700) BlockPlacementPolicy shoud choose storage but not datanode for deletion

[ https://issues.apache.org/jira/browse/HDFS-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-6700: -- Attachment: h6700_20140717.patch h6700_20140717.patch: changes to choose storages.

[jira] [Updated] (HDFS-6700) BlockPlacementPolicy shoud choose storage but not datanode for deletion

[ https://issues.apache.org/jira/browse/HDFS-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-6700: -- Status: Patch Available (was: Open) BlockPlacementPolicy shoud choose storage but not

[jira] [Created] (HDFS-6700) BlockPlacementPolicy shoud choose storage but not datanode for deletion

Tsz Wo Nicholas Sze created HDFS-6700: - Summary: BlockPlacementPolicy shoud choose storage but not datanode for deletion Key: HDFS-6700 URL: https://issues.apache.org/jira/browse/HDFS-6700

[jira] [Updated] (HDFS-6700) BlockPlacementPolicy shoud choose storage but not datanode for deletion

[ https://issues.apache.org/jira/browse/HDFS-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-6700: -- Component/s: namenode BlockPlacementPolicy shoud choose storage but not datanode for

[jira] [Updated] (HDFS-6671) Archival Storage: Consider block storage policy in replicaiton

[ https://issues.apache.org/jira/browse/HDFS-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-6671: -- Attachment: h6671_20140717.patch h6671_20140717.patch: renames the chooseTarget methods

[jira] [Resolved] (HDFS-6671) Archival Storage: Consider block storage policy in replicaiton

[ https://issues.apache.org/jira/browse/HDFS-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze resolved HDFS-6671. --- Resolution: Fixed Fix Version/s: Archival Storage (HDFS-6584) Hadoop

[jira] [Commented] (HDFS-4154) BKJM: Two namenodes usng bkjm can race to create the version znode

[ https://issues.apache.org/jira/browse/HDFS-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064893#comment-14064893 ] Rakesh R commented on HDFS-4154: Hi [~yians], Yeah I got your point. In this case we need

[jira] [Commented] (HDFS-5624) Add HDFS tests for ACLs in combination with viewfs.

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

[jira] [Commented] (HDFS-2538) option to disable fsck dots

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

[jira] [Commented] (HDFS-6690) Deduplicate xattr names in memory

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

[jira] [Commented] (HDFS-6689) NFS doesn't return correct lookup access for directories

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

[jira] [Commented] (HDFS-4120) Add a new -skipSharedEditsCheck option for BootstrapStandby

[ https://issues.apache.org/jira/browse/HDFS-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064915#comment-14064915 ] Rakesh R commented on HDFS-4120: Hi [~vinayrpet], It looks like test case failure is not

[jira] [Commented] (HDFS-2538) option to disable fsck dots

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

[jira] [Commented] (HDFS-6690) Deduplicate xattr names in memory

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

[jira] [Commented] (HDFS-5624) Add HDFS tests for ACLs in combination with viewfs.

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

[jira] [Commented] (HDFS-6689) NFS doesn't return correct lookup access for directories

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

[jira] [Commented] (HDFS-4154) BKJM: Two namenodes usng bkjm can race to create the version znode

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

[jira] [Commented] (HDFS-6680) BlockPlacementPolicyDefault does not choose favored nodes correctly

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

[jira] [Work started] (HDFS-6509) distcp vs Data At Rest Encryption

[ https://issues.apache.org/jira/browse/HDFS-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-6509 started by Charles Lamb. distcp vs Data At Rest Encryption - Key: HDFS-6509 URL:

[jira] [Commented] (HDFS-6700) BlockPlacementPolicy shoud choose storage but not datanode for deletion

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

[jira] [Updated] (HDFS-4265) BKJM doesn't take advantage of speculative reads

[ https://issues.apache.org/jira/browse/HDFS-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HDFS-4265: --- Attachment: 004-HDFS-4265.patch BKJM doesn't take advantage of speculative reads

[jira] [Commented] (HDFS-4265) BKJM doesn't take advantage of speculative reads

[ https://issues.apache.org/jira/browse/HDFS-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064971#comment-14064971 ] Rakesh R commented on HDFS-4265: Thanks [~ikelly]. I have exposed 'readEntryTimeoutSec'

[jira] [Commented] (HDFS-4265) BKJM doesn't take advantage of speculative reads

[ https://issues.apache.org/jira/browse/HDFS-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064972#comment-14064972 ] Ivan Kelly commented on HDFS-4265: -- lgtm +1 BKJM doesn't take advantage of speculative

[jira] [Commented] (HDFS-4266) BKJM: Separate write and ack quorum

[ https://issues.apache.org/jira/browse/HDFS-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064990#comment-14064990 ] Rakesh R commented on HDFS-4266: Yes [~ikelly], you are right. I think setting BookKeeper's

[jira] [Resolved] (HDFS-6611) secure components have the wrong pid in their files

[ https://issues.apache.org/jira/browse/HDFS-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-6611. Resolution: Duplicate I've provided a workaround in HADOOP-9902. secure components have

[jira] [Commented] (HDFS-4265) BKJM doesn't take advantage of speculative reads

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

[jira] [Resolved] (HDFS-315) Allow simplified versioning for namenode and datanode metadata.

[ https://issues.apache.org/jira/browse/HDFS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-315. --- Resolution: Fixed I'm going to resolve this since FSimage and buddies have been version-ed for

[jira] [Commented] (HDFS-6114) Block Scan log rolling will never happen if blocks written continuously leading to huge size of dncp_block_verification.log.curr

[ https://issues.apache.org/jira/browse/HDFS-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065071#comment-14065071 ] Vinayakumar B commented on HDFS-6114: - Seems like there was a compilation error in this

[jira] [Resolved] (HDFS-188) DFS web UI does should have TAIL this block option

[ https://issues.apache.org/jira/browse/HDFS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-188. --- Resolution: Won't Fix I'm going to close this as Won't Fix. Tailing a file provides a

[jira] [Resolved] (HDFS-318) Building Hadoop results in a lot of warnings

[ https://issues.apache.org/jira/browse/HDFS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-318. --- Resolution: Incomplete I'm going to close this out as stale. A new jira should be re-opened

[jira] [Commented] (HDFS-6699) Secure Windows DFS read when client co-located on nodes with data (short-circuit reads)

[ https://issues.apache.org/jira/browse/HDFS-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065106#comment-14065106 ] Chris Nauroth commented on HDFS-6699: - Thanks for filing this, Remus. At a high level,

[jira] [Resolved] (HDFS-25) The FSDirectory should not have waitForReady

[ https://issues.apache.org/jira/browse/HDFS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-25. -- Resolution: Incomplete I'm going to close this out as stale. I suspect this is no longer an

[jira] [Resolved] (HDFS-149) TestDFSUpgrade fails once in a while

[ https://issues.apache.org/jira/browse/HDFS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-149. --- Resolution: Fixed I'm going to close this out as stale. I suspect this is no longer an issue.

[jira] [Commented] (HDFS-6695) Investigate using Java 7's nonblocking file I/O in BlockReaderLocal to implement read timeouts

[ https://issues.apache.org/jira/browse/HDFS-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065173#comment-14065173 ] Chris Nauroth commented on HDFS-6695: - I'm linking this to HADOOP-9590, which was

[jira] [Resolved] (HDFS-68) TestDFSUpgrade fails sporadically in nightly and patch builds

[ https://issues.apache.org/jira/browse/HDFS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-68. -- Resolution: Incomplete Stale. Closing TestDFSUpgrade fails sporadically in nightly and patch

[jira] [Updated] (HDFS-6478) RemoteException can't be retried properly for non-HA scenario

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

[jira] [Commented] (HDFS-6699) Secure Windows DFS read when client co-located on nodes with data (short-circuit reads)

[ https://issues.apache.org/jira/browse/HDFS-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065208#comment-14065208 ] Arpit Agarwal commented on HDFS-6699: - Hi Remus, an alternative approach you may have

[jira] [Resolved] (HDFS-242) Improve debugabillity

[ https://issues.apache.org/jira/browse/HDFS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-242. --- Resolution: Incomplete I'm going to close this as stale. Many more metrics are now pumped up

[jira] [Commented] (HDFS-6478) RemoteException can't be retried properly for non-HA scenario

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

[jira] [Resolved] (HDFS-261) Side classes should be moved to separate files

[ https://issues.apache.org/jira/browse/HDFS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-261. --- Resolution: Incomplete Given the number of changes in source code layout, the switch to maven,

[jira] [Resolved] (HDFS-180) namenode -format does not reset version

[ https://issues.apache.org/jira/browse/HDFS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-180. --- Resolution: Fixed Fairly confident this has been fixed. namenode -format does not reset

[jira] [Resolved] (HDFS-295) Update the how to configure HDFS documentation to include new features

[ https://issues.apache.org/jira/browse/HDFS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-295. --- Resolution: Fixed ... and in 7 years, no one has been able to configure this stuff. ;)

[jira] [Commented] (HDFS-321) All FileSystem implementations should return Paths fully-qualified with scheme and host

[ https://issues.apache.org/jira/browse/HDFS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065236#comment-14065236 ] Allen Wittenauer commented on HDFS-321: --- Does that work still need to happen? All

[jira] [Commented] (HDFS-6699) Secure Windows DFS read when client co-located on nodes with data (short-circuit reads)

[ https://issues.apache.org/jira/browse/HDFS-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065255#comment-14065255 ] Chris Nauroth commented on HDFS-6699: - Thanks for pointing that out, Arpit. From my

[jira] [Commented] (HDFS-6699) Secure Windows DFS read when client co-located on nodes with data (short-circuit reads)

[ https://issues.apache.org/jira/browse/HDFS-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065269#comment-14065269 ] Remus Rusanu commented on HDFS-6699: [~arpitagarwal] I didn't consider mmap and

[jira] [Commented] (HDFS-6699) Secure Windows DFS read when client co-located on nodes with data (short-circuit reads)

[ https://issues.apache.org/jira/browse/HDFS-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065283#comment-14065283 ] Remus Rusanu commented on HDFS-6699: Also if the hdfs client ever impersonates

[jira] [Resolved] (HDFS-390) Hadoop daemons should support generic command-line options by implementing the Tool interface

[ https://issues.apache.org/jira/browse/HDFS-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-390. --- Resolution: Fixed This was done a long time ago. Hadoop daemons should support generic

[jira] [Commented] (HDFS-6695) Investigate using Java 7's nonblocking file I/O in BlockReaderLocal to implement read timeouts

[ https://issues.apache.org/jira/browse/HDFS-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065288#comment-14065288 ] Colin Patrick McCabe commented on HDFS-6695: bq. I did not look through

[jira] [Resolved] (HDFS-354) Data node process consumes 180% cpu

[ https://issues.apache.org/jira/browse/HDFS-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-354. --- Resolution: Fixed I'm going to close this out as stale. There has been a lot of reworking of

[jira] [Commented] (HDFS-6698) try to optimize DFSInputStream.getFileLength()

[ https://issues.apache.org/jira/browse/HDFS-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065300#comment-14065300 ] stack commented on HDFS-6698: - Makes sense [~xieliang007] You see this as prob in prod?

[jira] [Commented] (HDFS-270) DFS Upgrade should process dfs.data.dirs in parallel

[ https://issues.apache.org/jira/browse/HDFS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065304#comment-14065304 ] Allen Wittenauer commented on HDFS-270: --- Is this effectively close-able now? DFS

[jira] [Resolved] (HDFS-170) TestCrcCorruption sometimes fails

[ https://issues.apache.org/jira/browse/HDFS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-170. --- Resolution: Fixed I'm going to close this as stale. TestCrcCorruption sometimes fails

[jira] [Resolved] (HDFS-150) Replication should be decoupled from heartbeat

[ https://issues.apache.org/jira/browse/HDFS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-150. --- Resolution: Fixed Closing as fixed then! Replication should be decoupled from heartbeat

[jira] [Resolved] (HDFS-270) DFS Upgrade should process dfs.data.dirs in parallel

[ https://issues.apache.org/jira/browse/HDFS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HDFS-270. Resolution: Won't Fix I agree with resolving this. I'm resolving this as won't fix, but others can

[jira] [Resolved] (HDFS-281) Explore usage of the sendfile api via java.nio.channels.FileChannel.transfer{To|From} for i/o in datanodes

[ https://issues.apache.org/jira/browse/HDFS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-281. --- Resolution: Won't Fix I'm going to close this as a duplicate of HDFS-2246. While the path

[jira] [Commented] (HDFS-6616) bestNode shouldn't always return the first DataNode

[ https://issues.apache.org/jira/browse/HDFS-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065368#comment-14065368 ] Tsz Wo Nicholas Sze commented on HDFS-6616: --- Patch looks good. Some comments: -

[jira] [Commented] (HDFS-6616) bestNode shouldn't always return the first DataNode

[ https://issues.apache.org/jira/browse/HDFS-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065382#comment-14065382 ] Jing Zhao commented on HDFS-6616: - bq. We should also change WebHdfsFileSystem to use the

[jira] [Commented] (HDFS-310) Validate configuration parameters

[ https://issues.apache.org/jira/browse/HDFS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065384#comment-14065384 ] Allen Wittenauer commented on HDFS-310: --- Ping! Since this discussion, there have been

[jira] [Commented] (HDFS-2256) we should add a wait for non-safe mode and call dfsadmin -report in start-dfs

[ https://issues.apache.org/jira/browse/HDFS-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065385#comment-14065385 ] Allen Wittenauer commented on HDFS-2256: Is start-dfs.sh the right place for this

[jira] [Commented] (HDFS-6114) Block Scan log rolling will never happen if blocks written continuously leading to huge size of dncp_block_verification.log.curr

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

[jira] [Updated] (HDFS-6700) BlockPlacementPolicy shoud choose storage but not datanode for deletion

[ https://issues.apache.org/jira/browse/HDFS-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-6700: -- Attachment: h6700_20140717b.patch h6700_20140717b.patch: fixes TestReplicationPolicy

[jira] [Updated] (HDFS-394) NameNode shoud give the DataNodes a parameter that specifies the backoff time for initial block reports

[ https://issues.apache.org/jira/browse/HDFS-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-394: -- Summary: NameNode shoud give the DataNodes a parameter that specifies the backoff time for

[jira] [Updated] (HDFS-6693) TestDFSAdminWithHA fails on windows

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

[jira] [Updated] (HDFS-163) HDFS shell commands not as expected

[ https://issues.apache.org/jira/browse/HDFS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-163: -- Labels: newbie (was: ) HDFS shell commands not as expected

[jira] [Commented] (HDFS-163) HDFS shell commands not as expected

[ https://issues.apache.org/jira/browse/HDFS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065404#comment-14065404 ] Allen Wittenauer commented on HDFS-163: --- I suspect most of these have been fixed, but

[jira] [Commented] (HDFS-6693) TestDFSAdminWithHA fails on windows

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

[jira] [Resolved] (HDFS-383) Modify datanode configs to specify minimum JVM heapsize

[ https://issues.apache.org/jira/browse/HDFS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-383. --- Resolution: Fixed This was fixed with the introduction of HADOOP_DATANODE_OPTS and related env

[jira] [Commented] (HDFS-157) dfs client -ls/-lsr outofmemory when one directory contained 2 million files.

[ https://issues.apache.org/jira/browse/HDFS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065417#comment-14065417 ] Allen Wittenauer commented on HDFS-157: --- Is this still an issue? One fix is to use

[jira] [Resolved] (HDFS-356) Short -metasave option

[ https://issues.apache.org/jira/browse/HDFS-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-356. --- Resolution: Fixed I'm going to close out given that a lot/most/all of this information is

[jira] [Resolved] (HDFS-32) testFilePermissions in TestDFSShell should shut down the mini dfs cluster when there is an error

[ https://issues.apache.org/jira/browse/HDFS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-32. -- Resolution: Fixed Likely a stale issue and fixed long ago. testFilePermissions in TestDFSShell

[jira] [Updated] (HDFS-6422) getfattr in CLI doesn't throw exception or return non-0 return code when xattr doesn't exist

[ https://issues.apache.org/jira/browse/HDFS-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Lamb updated HDFS-6422: --- Attachment: HDFS-6422.006.patch Fixed

[jira] [Commented] (HDFS-122) Namenode should let Datanode decide how to delete blocks.

[ https://issues.apache.org/jira/browse/HDFS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065458#comment-14065458 ] Allen Wittenauer commented on HDFS-122: --- I suspect this a bit stale and can probably

[jira] [Commented] (HDFS-139) Datanode block deletions can get starved.

[ https://issues.apache.org/jira/browse/HDFS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065455#comment-14065455 ] Allen Wittenauer commented on HDFS-139: --- I suspect we can close this as fixed, but

[jira] [Resolved] (HDFS-54) datanode not failing when read-only filesystem

[ https://issues.apache.org/jira/browse/HDFS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-54. -- Resolution: Fixed Fairly confident this has been fixed. datanode not failing when read-only

[jira] [Commented] (HDFS-247) A tool to plot the locations of the blocks of a directory

[ https://issues.apache.org/jira/browse/HDFS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065505#comment-14065505 ] Allen Wittenauer commented on HDFS-247: --- It would be neat to be able to do this from

[jira] [Updated] (HDFS-247) A tool to plot the locations of the blocks of a directory

[ https://issues.apache.org/jira/browse/HDFS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-247: -- Labels: newbie (was: ) A tool to plot the locations of the blocks of a directory

[jira] [Commented] (HDFS-6699) Secure Windows DFS read when client co-located on nodes with data (short-circuit reads)

[ https://issues.apache.org/jira/browse/HDFS-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065536#comment-14065536 ] Arpit Agarwal commented on HDFS-6699: - Locking down the named mapping should be easy

[jira] [Resolved] (HDFS-24) FSDataOutputStream should flush last partial CRC chunk

[ https://issues.apache.org/jira/browse/HDFS-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-24. -- Resolution: Fixed I'd be greatly surprised if this wasn't fixed by now. FSDataOutputStream

[jira] [Commented] (HDFS-2364) metaSave API is using Printwriter, It will eat all the IOExceptions.

[ https://issues.apache.org/jira/browse/HDFS-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065576#comment-14065576 ] Allen Wittenauer commented on HDFS-2364: Ping! metaSave API is using Printwriter,

[jira] [Resolved] (HDFS-363) list of dead nodes with time information

[ https://issues.apache.org/jira/browse/HDFS-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-363. --- Resolution: Duplicate Closing as a dupe, then. list of dead nodes with time information

[jira] [Resolved] (HDFS-43) Ignoring IOExceptions on close

[ https://issues.apache.org/jira/browse/HDFS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-43. -- Resolution: Not a Problem Closing this as not a problem. Ignoring IOExceptions on close

[jira] [Resolved] (HDFS-137) DataNode should clean up temporary files when writeBlock fails.

[ https://issues.apache.org/jira/browse/HDFS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-137. --- Resolution: Fixed This has likely been fixed by now. DataNode should clean up temporary

[jira] [Resolved] (HDFS-374) HDFS needs to support a very large number of open files.

[ https://issues.apache.org/jira/browse/HDFS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-374. --- Resolution: Fixed I'm going to resolve this as stale. There is a good chance this issue might

[jira] [Resolved] (HDFS-306) FSNamesystem.shutdown() should be a part of FSNamesystem.close()

[ https://issues.apache.org/jira/browse/HDFS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-306. --- Resolution: Fixed I'm sure is this is fixed by now. FSNamesystem.shutdown() should be a part

[jira] [Commented] (HDFS-6268) Better sorting in NetworkTopology#pseudoSortByDistance when no local node is found

[ https://issues.apache.org/jira/browse/HDFS-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065630#comment-14065630 ] Ashwin Shankar commented on HDFS-6268: -- Hi [~andrew.wang], After applying your patch

[jira] [Resolved] (HDFS-337) Name collision for AccessControlException.

[ https://issues.apache.org/jira/browse/HDFS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-337. --- Resolution: Won't Fix Closing as won't fix, assuming we haven't already. Name collision for

[jira] [Resolved] (HDFS-296) Serial streaming performance should be Math.min(ideal client performance, ideal serial hdfs performance)

[ https://issues.apache.org/jira/browse/HDFS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-296. --- Resolution: Incomplete I'm going to close this as stale given how many changes have happened

[jira] [Assigned] (HDFS-6632) Remove incompatibility introduced by HDFS-5321

[ https://issues.apache.org/jira/browse/HDFS-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang reassigned HDFS-6632: --- Assignee: Yongjun Zhang Remove incompatibility introduced by HDFS-5321

[jira] [Resolved] (HDFS-338) When a block is severely under replicated at creation time, a request for block replication should be scheduled immediately

[ https://issues.apache.org/jira/browse/HDFS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HDFS-338. --- Resolution: Fixed Closing this as stale. When a block is severely under replicated at

[jira] [Commented] (HDFS-358) DataBlockScanner (via periodic verification) could be improved to check for corrupt block length

[ https://issues.apache.org/jira/browse/HDFS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065666#comment-14065666 ] Allen Wittenauer commented on HDFS-358: --- Is this still an issue? I seem to recall

[jira] [Commented] (HDFS-6700) BlockPlacementPolicy shoud choose storage but not datanode for deletion

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

[jira] [Updated] (HDFS-373) Name node should notify administrator if when struggling with replication

[ https://issues.apache.org/jira/browse/HDFS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-373: -- Labels: newbie (was: ) Name node should notify administrator if when struggling with

  1   2   >