[jira] [Commented] (HDFS-6742) Support sorting datanode list on the new NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074126#comment-14074126 ] Ming Ma commented on HDFS-6742: --- Arpit, good point. Let me follow up. Support sorting

[jira] [Created] (HDFS-6751) NN WebUI enhancements

Ming Ma created HDFS-6751: - Summary: NN WebUI enhancements Key: HDFS-6751 URL: https://issues.apache.org/jira/browse/HDFS-6751 Project: Hadoop HDFS Issue Type: Task Reporter: Ming Ma

[jira] [Updated] (HDFS-6742) Support sorting datanode list on the new NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma updated HDFS-6742: -- Issue Type: Sub-task (was: Improvement) Parent: HDFS-6751 Support sorting datanode list on the new NN

[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma updated HDFS-6743: -- Issue Type: Sub-task (was: Improvement) Parent: HDFS-6751 Put IP address into a new column on the new

[jira] [Updated] (HDFS-6744) Improve decommissioning nodes and dead nodes access on the new NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma updated HDFS-6744: -- Issue Type: Sub-task (was: Improvement) Parent: HDFS-6751 Improve decommissioning nodes and dead

[jira] [Updated] (HDFS-6745) Display the list of very-under-replicated blocks as well as the files on NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma updated HDFS-6745: -- Issue Type: Sub-task (was: Improvement) Parent: HDFS-6751 Display the list of very-under-replicated

[jira] [Commented] (HDFS-6745) Display the list of very-under-replicated blocks as well as the files on NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074139#comment-14074139 ] Ming Ma commented on HDFS-6745: --- CLI will be good. Perhaps people can also specify input

[jira] [Updated] (HDFS-6746) Support datanode list pagination and filtering for big clusters on NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma updated HDFS-6746: -- Issue Type: Sub-task (was: Improvement) Parent: HDFS-6751 Support datanode list pagination and

[jira] [Resolved] (HDFS-6747) Display the most recent GC info on NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma resolved HDFS-6747. --- Resolution: Won't Fix Display the most recent GC info on NN webUI

[jira] [Updated] (HDFS-6722) Display readable last contact time for dead nodes on NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma updated HDFS-6722: -- Issue Type: Sub-task (was: Improvement) Parent: HDFS-6751 Display readable last contact time for dead

[jira] [Commented] (HDFS-5919) FileJournalManager doesn't purge empty and corrupt inprogress edits files

[ https://issues.apache.org/jira/browse/HDFS-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074150#comment-14074150 ] Vinayakumar B commented on HDFS-5919: - Committed to trunk and branch-2. Thanks

[jira] [Updated] (HDFS-5919) FileJournalManager doesn't purge empty and corrupt inprogress edits files

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

[jira] [Commented] (HDFS-5919) FileJournalManager doesn't purge empty and corrupt inprogress edits files

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

[jira] [Commented] (HDFS-5919) FileJournalManager doesn't purge empty and corrupt inprogress edits files

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

[jira] [Created] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

Vinayakumar B created HDFS-6752: --- Summary: Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit Key: HDFS-6752 URL: https://issues.apache.org/jira/browse/HDFS-6752 Project: Hadoop HDFS

[jira] [Updated] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HDFS-6752: Attachment: HDFS-6752.patch Attaching the patch to configure datanode port as ephemeral Avoid

[jira] [Updated] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HDFS-6752: Status: Patch Available (was: Open) Avoid Address bind errors in

[jira] [Commented] (HDFS-6747) Display the most recent GC info on NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074178#comment-14074178 ] Haohui Mai commented on HDFS-6747: -- I think that it will be quite handy to show some GC

[jira] [Commented] (HDFS-5919) FileJournalManager doesn't purge empty and corrupt inprogress edits files

[ https://issues.apache.org/jira/browse/HDFS-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074188#comment-14074188 ] Vinayakumar B commented on HDFS-5919: - Above failures are not related this patch. bq.

[jira] [Commented] (HDFS-6709) Implement off-heap data structures for NameNode and other HDFS memory optimization

[ https://issues.apache.org/jira/browse/HDFS-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074189#comment-14074189 ] Kai Zheng commented on HDFS-6709: - I repeated the test in the post and sadly found it's

[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=14074250#comment-14074250 ] Rakesh R commented on HDFS-4265: Hi [~umamaheswararao] Could you please have a look at this

[jira] [Commented] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

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

[jira] [Commented] (HDFS-6723) New NN webUI no longer displays decommissioned state for dead node

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

[jira] [Commented] (HDFS-5919) FileJournalManager doesn't purge empty and corrupt inprogress edits files

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

[jira] [Commented] (HDFS-6657) Remove link to 'Legacy UI' in trunk's Namenode UI

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

[jira] [Commented] (HDFS-6715) webhdfs wont fail over when it gets java.io.IOException: Namenode is in startup mode

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

[jira] [Created] (HDFS-6753) When one the Disk is full and all the volumes configured are unhealthy , then Datanode is not considering it as failure and datanode process is not shutting down .

J.Andreina created HDFS-6753: Summary: When one the Disk is full and all the volumes configured are unhealthy , then Datanode is not considering it as failure and datanode process is not shutting down . Key: HDFS-6753

[jira] [Commented] (HDFS-5919) FileJournalManager doesn't purge empty and corrupt inprogress edits files

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

[jira] [Commented] (HDFS-6723) New NN webUI no longer displays decommissioned state for dead node

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

[jira] [Commented] (HDFS-6657) Remove link to 'Legacy UI' in trunk's Namenode UI

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

[jira] [Commented] (HDFS-6715) webhdfs wont fail over when it gets java.io.IOException: Namenode is in startup mode

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

[jira] [Commented] (HDFS-6723) New NN webUI no longer displays decommissioned state for dead node

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

[jira] [Commented] (HDFS-6657) Remove link to 'Legacy UI' in trunk's Namenode UI

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

[jira] [Commented] (HDFS-5919) FileJournalManager doesn't purge empty and corrupt inprogress edits files

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

[jira] [Commented] (HDFS-6715) webhdfs wont fail over when it gets java.io.IOException: Namenode is in startup mode

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

[jira] [Commented] (HDFS-6247) Avoid timeouts for replaceBlock() call by sending intermediate responses to Balancer

[ https://issues.apache.org/jira/browse/HDFS-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074441#comment-14074441 ] Charles Lamb commented on HDFS-6247: 30 seconds would be fine, or maybe even some time

[jira] [Updated] (HDFS-6749) FSNamesystem#getXAttrs and listXAttrs should call resolvePath

[ https://issues.apache.org/jira/browse/HDFS-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Lamb updated HDFS-6749: --- Attachment: HDFS-6749.002.patch [~cnauroth], Thanks for the review and that's a good point about

[jira] [Moved] (HDFS-6754) TestNamenodeCapacityReport.testXceiverCount may sometimes fail due to lack of retry

[ https://issues.apache.org/jira/browse/HDFS-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai moved YARN-2358 to HDFS-6754: --- Target Version/s: 2.6.0 (was: 2.6.0) Affects Version/s: (was: 2.6.0)

[jira] [Created] (HDFS-6755) Make DFSOutputStream more efficient

Mit Desai created HDFS-6755: --- Summary: Make DFSOutputStream more efficient Key: HDFS-6755 URL: https://issues.apache.org/jira/browse/HDFS-6755 Project: Hadoop HDFS Issue Type: Bug Affects

[jira] [Updated] (HDFS-6755) Make DFSOutputStream more efficient

[ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated HDFS-6755: Issue Type: Improvement (was: Bug) Make DFSOutputStream more efficient

[jira] [Updated] (HDFS-6755) Make DFSOutputStream more efficient

[ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated HDFS-6755: Description: Following code in DFSOutputStream may have an unnecessary sleep. {code} try {

[jira] [Commented] (HDFS-6750) The DataNode should use its shared memory segment to mark short-circuit replicas that have been unlinked as stale

[ https://issues.apache.org/jira/browse/HDFS-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074587#comment-14074587 ] Colin Patrick McCabe commented on HDFS-6750: Test failures are unrelated.

[jira] [Commented] (HDFS-6729) Support maintenance mode for DN

[ https://issues.apache.org/jira/browse/HDFS-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074651#comment-14074651 ] Colin Patrick McCabe commented on HDFS-6729: By default it takes 10 and a half

[jira] [Commented] (HDFS-6742) Support sorting datanode list on the new NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074662#comment-14074662 ] Arpit Agarwal commented on HDFS-6742: - Thanks Ming! Support sorting datanode list on

[jira] [Commented] (HDFS-6247) Avoid timeouts for replaceBlock() call by sending intermediate responses to Balancer

[ https://issues.apache.org/jira/browse/HDFS-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074674#comment-14074674 ] Vinayakumar B commented on HDFS-6247: - I feel 30 seconds or may be 0.5 * socketTimeout

[jira] [Commented] (HDFS-583) HDFS should enforce a max block size

[ https://issues.apache.org/jira/browse/HDFS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074690#comment-14074690 ] Colin Patrick McCabe commented on HDFS-583: --- Most places where we refer to block

[jira] [Commented] (HDFS-6247) Avoid timeouts for replaceBlock() call by sending intermediate responses to Balancer

[ https://issues.apache.org/jira/browse/HDFS-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074693#comment-14074693 ] Charles Lamb commented on HDFS-6247: bq. II feel making at same as socketTimeout can

[jira] [Commented] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074694#comment-14074694 ] Arpit Agarwal commented on HDFS-6752: - +1 for the patch. Avoid Address bind errors in

[jira] [Updated] (HDFS-6247) Avoid timeouts for replaceBlock() call by sending intermediate responses to Balancer

[ https://issues.apache.org/jira/browse/HDFS-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HDFS-6247: Attachment: HDFS-6247.patch Attached the updated patch. Uses interval as {{0.5 * socketTimeout}}

[jira] [Commented] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074719#comment-14074719 ] Vinayakumar B commented on HDFS-6752: - Thanks [~arpit99] for the review. Will commit

[jira] [Commented] (HDFS-6755) Make DFSOutputStream more efficient

[ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074717#comment-14074717 ] Colin Patrick McCabe commented on HDFS-6755: The code here is using exponential

[jira] [Commented] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074722#comment-14074722 ] Vinayakumar B commented on HDFS-6752: - Oops!. Wrong tag. Thanks [~arpitagarwal] for

[jira] [Commented] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074729#comment-14074729 ] Vinayakumar B commented on HDFS-6752: - Committed to trunk and branch-2 Avoid Address

[jira] [Updated] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

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

[jira] [Commented] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

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

[jira] [Commented] (HDFS-6743) Put IP address into a new column on the new NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074734#comment-14074734 ] Chen He commented on HDFS-6743: --- Hi [~aw], are you working on this issue? If so, please

[jira] [Updated] (HDFS-6755) Make DFSOutputStream more efficient

[ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated HDFS-6755: Attachment: HDFS-6755.patch Hi [~cmccabe], I did not mean to get rid of the sleep. I have uploaded the

[jira] [Assigned] (HDFS-6742) Support sorting datanode list on the new NN webUI

[ https://issues.apache.org/jira/browse/HDFS-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He reassigned HDFS-6742: - Assignee: Chen He Support sorting datanode list on the new NN webUI

[jira] [Resolved] (HDFS-6724) Decrypt EDEK before creating CryptoInputStream/CryptoOutputStream

[ https://issues.apache.org/jira/browse/HDFS-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HDFS-6724. --- Resolution: Fixed Fix Version/s: fs-encryption (HADOOP-10150 and HDFS-6134) Decrypt EDEK

[jira] [Updated] (HDFS-6724) Decrypt EDEK before creating CryptoInputStream/CryptoOutputStream

[ https://issues.apache.org/jira/browse/HDFS-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-6724: -- Attachment: hdfs-6724.003.patch Thanks again for the reviews guys, attaching a final patch removing the

[jira] [Commented] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074758#comment-14074758 ] Arpit Agarwal commented on HDFS-6752: - Thanks for fixing this [~vinayrpet]. Since it

[jira] [Commented] (HDFS-6755) Make DFSOutputStream more efficient

[ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074759#comment-14074759 ] Colin Patrick McCabe commented on HDFS-6755: Ah. I misinterpreted your

[jira] [Updated] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

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

[jira] [Updated] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-6752: Affects Version/s: 3.0.0 Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[jira] [Commented] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074763#comment-14074763 ] Arpit Agarwal commented on HDFS-6752: - Merged to branch-2.5 as r1613492. Avoid

[jira] [Updated] (HDFS-6755) There is an unnecessary sleep in the code path where DFSOutputStream#close gives up its attempt to contact the namenode

[ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-6755: --- Description: DFSOutputStream#close has a loop where it tries to contact the NameNode,

[jira] [Updated] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-6752: Affects Version/s: 2.4.1 Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[jira] [Updated] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-6752: Component/s: test Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[jira] [Updated] (HDFS-6752) Avoid Address bind errors in TestDatanodeConfig#testMemlockLimit

[ https://issues.apache.org/jira/browse/HDFS-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-6752: Release Note: (was: Merged to branch-2.5 as r1613492.) Avoid Address bind errors in

[jira] [Updated] (HDFS-6755) There is an unnecessary sleep in the code path where DFSOutputStream#close gives up its attempt to contact the namenode

[ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-6755: --- Status: Patch Available (was: Open) There is an unnecessary sleep in the code path

[jira] [Updated] (HDFS-6755) There is an unnecessary sleep in the code path where DFSOutputStream#close gives up its attempt to contact the namenode

[ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-6755: --- Summary: There is an unnecessary sleep in the code path where DFSOutputStream#close

[jira] [Commented] (HDFS-6749) FSNamesystem#getXAttrs and listXAttrs should call resolvePath

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

[jira] [Commented] (HDFS-6749) FSNamesystem#getXAttrs and listXAttrs should call resolvePath

[ https://issues.apache.org/jira/browse/HDFS-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074770#comment-14074770 ] Charles Lamb commented on HDFS-6749: The test failure appears to be unrelated.

[jira] [Created] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

Juan Yu created HDFS-6756: - Summary: Default ipc.maximum.data.length should be increased to 128MB from 64MB Key: HDFS-6756 URL: https://issues.apache.org/jira/browse/HDFS-6756 Project: Hadoop HDFS

[jira] [Updated] (HDFS-4449) When a decommission is awaiting closure of live blocks, show the block IDs on the NameNode's UI report

[ https://issues.apache.org/jira/browse/HDFS-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-4449: -- Assignee: Yongjun Zhang (was: Harsh J) When a decommission is awaiting closure of live blocks, show the block

[jira] [Commented] (HDFS-964) hdfs-default.xml shouldn't use hadoop.tmp.dir for dfs.data.dir (0.20 and lower) / dfs.datanode.dir (0.21 and up)

[ https://issues.apache.org/jira/browse/HDFS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074787#comment-14074787 ] Juan Yu commented on HDFS-964: -- Hi [~aw], this seems a good idea, why is it marked as Won't

[jira] [Commented] (HDFS-223) Asynchronous IO Handling in Hadoop and HDFS

[ https://issues.apache.org/jira/browse/HDFS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074837#comment-14074837 ] Colin Patrick McCabe commented on HDFS-223: --- I think the existing thread-pool

[jira] [Commented] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

[ https://issues.apache.org/jira/browse/HDFS-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074853#comment-14074853 ] Arpit Agarwal commented on HDFS-6756: - Hi Juan, are you seeing any specific instance

[jira] [Commented] (HDFS-223) Asynchronous IO Handling in Hadoop and HDFS

[ https://issues.apache.org/jira/browse/HDFS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074856#comment-14074856 ] Andrew Purtell commented on HDFS-223: - Agreed. CPU becomes more of an issue if the block

[jira] [Commented] (HDFS-6247) Avoid timeouts for replaceBlock() call by sending intermediate responses to Balancer

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

[jira] [Updated] (HDFS-6740) FSDataset adds data volumes dynamically

[ https://issues.apache.org/jira/browse/HDFS-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei (Eddy) Xu updated HDFS-6740: Attachment: HDFS-6740.000.patch Upload patch that supports adding volumes to

[jira] [Commented] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

[ https://issues.apache.org/jira/browse/HDFS-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074937#comment-14074937 ] Juan Yu commented on HDFS-6756: --- Got lots of messages like Requested data length 72293417 is

[jira] [Commented] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

[ https://issues.apache.org/jira/browse/HDFS-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074969#comment-14074969 ] Arpit Agarwal commented on HDFS-6756: - Did you figure out which specific RPC call? Was

[jira] [Comment Edited] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

[ https://issues.apache.org/jira/browse/HDFS-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074969#comment-14074969 ] Arpit Agarwal edited comment on HDFS-6756 at 7/25/14 9:37 PM: --

[jira] [Updated] (HDFS-6570) add api that enables checking if a user has certain permissions on a file

[ https://issues.apache.org/jira/browse/HDFS-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-6570: --- Status: Open (was: Patch Available) add api that enables checking if a user has

[jira] [Commented] (HDFS-6755) There is an unnecessary sleep in the code path where DFSOutputStream#close gives up its attempt to contact the namenode

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

[jira] [Updated] (HDFS-6570) add api that enables checking if a user has certain permissions on a file

[ https://issues.apache.org/jira/browse/HDFS-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-6570: --- Attachment: HDFS-6570.4.patch Thanks for the reviews Chris. Updated patch addresses

[jira] [Updated] (HDFS-6570) add api that enables checking if a user has certain permissions on a file

[ https://issues.apache.org/jira/browse/HDFS-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-6570: --- Status: Patch Available (was: Open) add api that enables checking if a user has

[jira] [Commented] (HDFS-6729) Support maintenance mode for DN

[ https://issues.apache.org/jira/browse/HDFS-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075005#comment-14075005 ] Lei (Eddy) Xu commented on HDFS-6729: - [~aw] and [~cmccabe] Thanks for looking into

[jira] [Commented] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

[ https://issues.apache.org/jira/browse/HDFS-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075019#comment-14075019 ] Juan Yu commented on HDFS-6756: --- [~arpitagarwal] You're right, this is in block report, this

[jira] [Commented] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

[ https://issues.apache.org/jira/browse/HDFS-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075023#comment-14075023 ] Arpit Agarwal commented on HDFS-6756: - HDFS-5153 Default ipc.maximum.data.length

[jira] [Commented] (HDFS-6755) There is an unnecessary sleep in the code path where DFSOutputStream#close gives up its attempt to contact the namenode

[ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075029#comment-14075029 ] Colin Patrick McCabe commented on HDFS-6755: No new tests are needed, since

[jira] [Commented] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

[ https://issues.apache.org/jira/browse/HDFS-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075037#comment-14075037 ] Juan Yu commented on HDFS-6756: --- Thx a lot. One more question, The split is per storage

[jira] [Resolved] (HDFS-3607) log a message when fuse_dfs is not built

[ https://issues.apache.org/jira/browse/HDFS-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe resolved HDFS-3607. Resolution: Fixed Target Version/s: (was: ) log a message when

[jira] [Commented] (HDFS-6755) There is an unnecessary sleep in the code path where DFSOutputStream#close gives up its attempt to contact the namenode

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

[jira] [Commented] (HDFS-3607) log a message when fuse_dfs is not built

[ https://issues.apache.org/jira/browse/HDFS-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075044#comment-14075044 ] Colin Patrick McCabe commented on HDFS-3607: We now do log a message when fuse

[jira] [Commented] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

[ https://issues.apache.org/jira/browse/HDFS-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075051#comment-14075051 ] Arpit Agarwal commented on HDFS-6756: - Possible but unlikely in the near future at

[jira] [Resolved] (HDFS-6756) Default ipc.maximum.data.length should be increased to 128MB from 64MB

[ https://issues.apache.org/jira/browse/HDFS-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Yu resolved HDFS-6756. --- Resolution: Invalid Default ipc.maximum.data.length should be increased to 128MB from 64MB

[jira] [Updated] (HDFS-3607) log a message when fuse_dfs is not built

[ https://issues.apache.org/jira/browse/HDFS-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-3607: --- Target Version/s: 2.0.2-alpha Fix Version/s: 2.0.2-alpha log a message when

[jira] [Commented] (HDFS-3607) log a message when fuse_dfs is not built

[ https://issues.apache.org/jira/browse/HDFS-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075060#comment-14075060 ] Colin Patrick McCabe commented on HDFS-3607: This was fixed by HADOOP-8368.

  1   2   >