[jira] [Created] (HDFS-9617) my java client use muti-thread to put a same file to a same hdfs uri, after no lease error，then client OutOfMemoryError

zuotingbing created HDFS-9617: - Summary: my java client use muti-thread to put a same file to a same hdfs uri, after no lease error，then client OutOfMemoryError Key: HDFS-9617 URL:

[jira] [Commented] (HDFS-9005) Provide support for upgrade domain script

[ https://issues.apache.org/jira/browse/HDFS-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085290#comment-15085290 ] Hadoop QA commented on HDFS-9005: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085335#comment-15085335 ] Masatake Iwasaki commented on HDFS-9618: The log level had been info but it seemed to be changed to

[jira] [Commented] (HDFS-7661) Erasure coding: support hflush and hsync

[ https://issues.apache.org/jira/browse/HDFS-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085202#comment-15085202 ] Walter Su commented on HDFS-7661: - You totally miss my point. A successful flush is a guarantee that the

[jira] [Commented] (HDFS-8999) Namenode need not wait for {{blockReceived}} for the last block before completing a file.

[ https://issues.apache.org/jira/browse/HDFS-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085316#comment-15085316 ] Tsz Wo Nicholas Sze commented on HDFS-8999: --- > 2. Should we be more aggressive and allow all the

[jira] [Commented] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085324#comment-15085324 ] Masatake Iwasaki commented on HDFS-9618: {code} if (blockLog.isInfoEnabled()) { // log

[jira] [Commented] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085371#comment-15085371 ] Kai Zheng commented on HDFS-9618: - Good catch! The pattern to use {{logger.isInfoEnabled}} shouldn't be

[jira] [Created] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

Masatake Iwasaki created HDFS-9618: -- Summary: Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks Key: HDFS-9618 URL: https://issues.apache.org/jira/browse/HDFS-9618

[jira] [Commented] (HDFS-7661) Erasure coding: support hflush and hsync

[ https://issues.apache.org/jira/browse/HDFS-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085278#comment-15085278 ] GAO Rui commented on HDFS-7661: --- Thank you [~walter.k.su]. I understand your concern now. You are right, in

[jira] [Updated] (HDFS-8999) Namenode need not wait for {{blockReceived}} for the last block before completing a file.

[ https://issues.apache.org/jira/browse/HDFS-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-8999: -- Attachment: h8999_20160106b.patch h8999_20160106b.patch: addresses Jing's comment. >

[jira] [Commented] (HDFS-9279) Decomissioned capacity should not be considered for configured/used capacity

[ https://issues.apache.org/jira/browse/HDFS-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085445#comment-15085445 ] Rajat Jain commented on HDFS-9279: -- While it makes sense to not include decommissioning nodes in

[jira] [Commented] (HDFS-9617) my java client use muti-thread to put a same file to a same hdfs uri, after no lease error，then client OutOfMemoryError

[ https://issues.apache.org/jira/browse/HDFS-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085526#comment-15085526 ] Kai Zheng commented on HDFS-9617: - Thanks for reporting this. bq. my java client use muti-thread to put a

[jira] [Commented] (HDFS-9279) Decomissioned capacity should not be considered for configured/used capacity

[ https://issues.apache.org/jira/browse/HDFS-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085577#comment-15085577 ] Kihwal Lee commented on HDFS-9279: -- bq. Because the data present in the decommissioning nodes would

[jira] [Commented] (HDFS-8999) Namenode need not wait for {{blockReceived}} for the last block before completing a file.

[ https://issues.apache.org/jira/browse/HDFS-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085482#comment-15085482 ] Hadoop QA commented on HDFS-8999: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (HDFS-9612) DistCp worker threads are not terminated after jobs are done.

[ https://issues.apache.org/jira/browse/HDFS-9612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-9612: -- Attachment: HDFS-9612.005.patch Rev05: added @throws to make Javadoc happy. > DistCp worker

[jira] [Commented] (HDFS-9612) DistCp worker threads are not terminated after jobs are done.

[ https://issues.apache.org/jira/browse/HDFS-9612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085507#comment-15085507 ] Hadoop QA commented on HDFS-9612: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (HDFS-8999) Namenode need not wait for {{blockReceived}} for the last block before completing a file.

[ https://issues.apache.org/jira/browse/HDFS-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-8999: -- Attachment: h8999_20160106c.patch h8999_20160106c.patch: fixes a NPE. > Namenode need

[jira] [Commented] (HDFS-8999) Namenode need not wait for {{blockReceived}} for the last block before completing a file.

[ https://issues.apache.org/jira/browse/HDFS-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085715#comment-15085715 ] Hadoop QA commented on HDFS-8999: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (HDFS-9576) HTrace: collect path/offset/length information on read and write operations

[ https://issues.apache.org/jira/browse/HDFS-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085932#comment-15085932 ] Masatake Iwasaki commented on HDFS-9576: I agree to fix tracing of write in follow-up. The 02

[jira] [Updated] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-9619: -- Description: We sometimes see {{TestBalancerWithMultipleNameNodes.testBalancer}} failed to

[jira] [Commented] (HDFS-9615) Fix variable name typo in DFSConfigKeys

[ https://issues.apache.org/jira/browse/HDFS-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085943#comment-15085943 ] Ray Chiang commented on HDFS-9615: -- Thanks for the review and the commit! > Fix variable name typo in

[jira] [Updated] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-9619: -- Description: We sometimes see {{TestBalancerWithMultipleNameNodes.testBalancer}} failed to

[jira] [Updated] (HDFS-9498) Move code that tracks blocks with future generation stamps to BlockManagerSafeMode

[ https://issues.apache.org/jira/browse/HDFS-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-9498: Summary: Move code that tracks blocks with future generation stamps to BlockManagerSafeMode (was:

[jira] [Commented] (HDFS-9576) HTrace: collect position/length information on read operations

[ https://issues.apache.org/jira/browse/HDFS-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086016#comment-15086016 ] Xiao Chen commented on HDFS-9576: - Thanks for the work, and sorry for jumping in. {code}

[jira] [Updated] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki updated HDFS-9618: --- Attachment: HDFS-9618.001.patch Thanks for the comment, [~drankye]. I attached 001. bq. Then

[jira] [Updated] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki updated HDFS-9618: --- Affects Version/s: (was: 3.0.0) 2.8.0 Status: Patch

[jira] [Updated] (HDFS-9576) HTrace: collect position/length information on read operations

[ https://issues.apache.org/jira/browse/HDFS-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-9576: Attachment: HDFS-9576.04.patch Thanks Xiao for the good catch! Updating the patch to address. Also renaming

[jira] [Commented] (HDFS-9576) HTrace: collect position/length information on read operations

[ https://issues.apache.org/jira/browse/HDFS-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086033#comment-15086033 ] Hadoop QA commented on HDFS-9576: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086043#comment-15086043 ] Mingliang Liu commented on HDFS-9618: - Thanks for working on this, [~iwasakims]i]. Calling

[jira] [Updated] (HDFS-9498) Move code that tracks blocks with future generation stamps to BlockManagerSafeMode

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

[jira] [Commented] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086050#comment-15086050 ] Mingliang Liu commented on HDFS-9618: - We have 5 levels of priority queues and the aggregation should

[jira] [Commented] (HDFS-9498) Move code that tracks blocks with future generation stamps to BlockManagerSafeMode

[ https://issues.apache.org/jira/browse/HDFS-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086055#comment-15086055 ] Mingliang Liu commented on HDFS-9498: - Thank you [~arpitagarwal] for your insightful comments and

[jira] [Commented] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086063#comment-15086063 ] Mingliang Liu commented on HDFS-9618: - +1 (non-binding) > Fix mismatch between log level and guard in

[jira] [Updated] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingliang Liu updated HDFS-9618: Component/s: namenode > Fix mismatch between log level and guard in >

[jira] [Commented] (HDFS-9617) my java client use muti-thread to put a same file to a same hdfs uri, after no lease error，then client OutOfMemoryError

[ https://issues.apache.org/jira/browse/HDFS-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086069#comment-15086069 ] Mingliang Liu commented on HDFS-9617: - If this is not yet confirmed a bug or a feature request, please

[jira] [Commented] (HDFS-9498) Move code that tracks blocks with future generation stamps to BlockManagerSafeMode

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

[jira] [Commented] (HDFS-8999) Namenode need not wait for {{blockReceived}} for the last block before completing a file.

[ https://issues.apache.org/jira/browse/HDFS-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086101#comment-15086101 ] Jing Zhao commented on HDFS-8999: - # How about making BlockNotYetCompleteException simply an IOException

[jira] [Updated] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-9619: -- Attachment: HDFS-9619.002.patch Rev02: Added a test case. In this test case

[jira] [Commented] (HDFS-9576) HTrace: collect position/length information on read operations

[ https://issues.apache.org/jira/browse/HDFS-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086111#comment-15086111 ] Hadoop QA commented on HDFS-9576: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (HDFS-9617) my java client use muti-thread to put a same file to a same hdfs uri, after no lease error，then client OutOfMemoryError

[ https://issues.apache.org/jira/browse/HDFS-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086124#comment-15086124 ] Kihwal Lee commented on HDFS-9617: -- bq. my java client use muti-thread to put a same file to a same hdfs

[jira] [Resolved] (HDFS-9617) my java client use muti-thread to put a same file to a same hdfs uri, after no lease error，then client OutOfMemoryError

[ https://issues.apache.org/jira/browse/HDFS-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee resolved HDFS-9617. -- Resolution: Invalid > my java client use muti-thread to put a same file to a same hdfs uri, after > no

[jira] [Commented] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086145#comment-15086145 ] Wei-Chiu Chuang commented on HDFS-9619: --- Well, maybe the test case is not needed. It's pretty obvious

[jira] [Updated] (HDFS-9615) Fix variable name typo in DFSConfigKeys

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

[jira] [Commented] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks

[ https://issues.apache.org/jira/browse/HDFS-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085978#comment-15085978 ] Masatake Iwasaki commented on HDFS-9618: This was wrong. The log level was changed by HDFS-6860. >

[jira] [Created] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

Wei-Chiu Chuang created HDFS-9619: - Summary: DataNode sometimes can not find blockpool for the correct namenode Key: HDFS-9619 URL: https://issues.apache.org/jira/browse/HDFS-9619 Project: Hadoop

[jira] [Commented] (HDFS-9498) Move code that tracks orphan blocks to BlockManagerSafeMode

[ https://issues.apache.org/jira/browse/HDFS-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085933#comment-15085933 ] Anu Engineer commented on HDFS-9498: +1 (non-binding), LGTM > Move code that tracks orphan blocks to

[jira] [Commented] (HDFS-9615) Fix variable name typo in DFSConfigKeys

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

[jira] [Updated] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-9619: -- Component/s: test datanode > DataNode sometimes can not find blockpool for the

[jira] [Updated] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-9619: -- Labels: test (was: ) > DataNode sometimes can not find blockpool for the correct namenode >

[jira] [Updated] (HDFS-9576) HTrace: collect path/offset/length information on read operations

[ https://issues.apache.org/jira/browse/HDFS-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-9576: Summary: HTrace: collect path/offset/length information on read operations (was: HTrace: collect

[jira] [Updated] (HDFS-9576) HTrace: collect path/offset/length information on read operations

[ https://issues.apache.org/jira/browse/HDFS-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-9576: Attachment: HDFS-9576.03.patch Good catch! Updating the patch to address. > HTrace: collect

[jira] [Updated] (HDFS-9576) HTrace: collect path/offset/length information on read operations

[ https://issues.apache.org/jira/browse/HDFS-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-9576: Description: HTrace currently collects the path of each read operation (both stateful and position reads).

[jira] [Updated] (HDFS-9576) HTrace: collect position/length information on read operations

[ https://issues.apache.org/jira/browse/HDFS-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-9576: Summary: HTrace: collect position/length information on read operations (was: HTrace: collect

[jira] [Updated] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-9619: -- Description: We sometimes see {{TestBalancerWithMultipleNameNodes.testBalancer}} failed to

[jira] [Updated] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-9619: -- Attachment: HDFS-9619.001.patch Rev01. Use ConcurrentHashMap instead of HashMap in

[jira] [Updated] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-9619: -- Status: Patch Available (was: Open) > DataNode sometimes can not find blockpool for the correct

[jira] [Commented] (HDFS-6142) StandbyException wrapped to InvalidToken exception

[ https://issues.apache.org/jira/browse/HDFS-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085867#comment-15085867 ] Kihwal Lee commented on HDFS-6142: -- bq. For example, in datanode's DataXceiver.copyBlock, it will call

[jira] [Commented] (HDFS-9276) Failed to Update HDFS Delegation Token for long running application in HA mode

[ https://issues.apache.org/jira/browse/HDFS-9276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085887#comment-15085887 ] Daryn Sharp commented on HDFS-9276: --- I'll be taking a look to ensure this doesn't break our IP-failover

[jira] [Updated] (HDFS-9615) Fix variable name typo in DFSConfigKeys

[ https://issues.apache.org/jira/browse/HDFS-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-9615: Summary: Fix variable name typo in DFSConfigKeys (was: Fix variable name typo in

[jira] [Commented] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086483#comment-15086483 ] Wei-Chiu Chuang commented on HDFS-9619: --- The failed tests appear to be flaky ones, unrelated to this

[jira] [Created] (HDFS-9621) {{getListing}} wrongly associates Erasure Coding policy to pre-existing replicated files under an EC directory

Jing Zhao created HDFS-9621: --- Summary: {{getListing}} wrongly associates Erasure Coding policy to pre-existing replicated files under an EC directory Key: HDFS-9621 URL:

[jira] [Updated] (HDFS-9621) getListing wrongly associates Erasure Coding policy to pre-existing replicated files under an EC directory

[ https://issues.apache.org/jira/browse/HDFS-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-9621: Summary: getListing wrongly associates Erasure Coding policy to pre-existing replicated files under an EC

[jira] [Updated] (HDFS-9621) getListing wrongly associates Erasure Coding policy to pre-existing replicated files under an EC directory

[ https://issues.apache.org/jira/browse/HDFS-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-9621: Priority: Critical (was: Blocker) > getListing wrongly associates Erasure Coding policy to pre-existing >

[jira] [Updated] (HDFS-9621) getListing wrongly associates Erasure Coding policy to pre-existing replicated files under an EC directory

[ https://issues.apache.org/jira/browse/HDFS-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-9621: Issue Type: Sub-task (was: Bug) Parent: HDFS-8031 > getListing wrongly associates Erasure Coding

[jira] [Updated] (HDFS-9047) Retire libwebhdfs

[ https://issues.apache.org/jira/browse/HDFS-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai updated HDFS-9047: - Summary: Retire libwebhdfs (was: deprecate libwebhdfs in branch-2; remove from trunk) > Retire

[jira] [Commented] (HDFS-8999) Namenode need not wait for {{blockReceived}} for the last block before completing a file.

[ https://issues.apache.org/jira/browse/HDFS-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086562#comment-15086562 ] Konstantin Shvachko commented on HDFS-8999: --- COMPLETE state used to mean that the number of

[jira] [Updated] (HDFS-9621) getListing wrongly associates Erasure Coding policy to pre-existing replicated files under an EC directory

[ https://issues.apache.org/jira/browse/HDFS-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-9621: Status: Patch Available (was: Open) > getListing wrongly associates Erasure Coding policy to pre-existing

[jira] [Updated] (HDFS-9314) Improve BlockPlacementPolicyDefault's picking of excess replicas

[ https://issues.apache.org/jira/browse/HDFS-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HDFS-9314: - Target Version/s: 2.6.4 > Improve BlockPlacementPolicyDefault's picking of excess replicas >

[jira] [Updated] (HDFS-8647) Abstract BlockManager's rack policy into BlockPlacementPolicy

[ https://issues.apache.org/jira/browse/HDFS-8647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HDFS-8647: - Target Version/s: 2.6.4 > Abstract BlockManager's rack policy into BlockPlacementPolicy >

[jira] [Commented] (HDFS-8999) Namenode need not wait for {{blockReceived}} for the last block before completing a file.

[ https://issues.apache.org/jira/browse/HDFS-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086570#comment-15086570 ] Konstantin Shvachko commented on HDFS-8999: --- > Let's test with the last block to see if it

[jira] [Updated] (HDFS-9621) getListing wrongly associates Erasure Coding policy to pre-existing replicated files under an EC directory

[ https://issues.apache.org/jira/browse/HDFS-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-9621: Attachment: HDFS-9621.000.patch Upload a patch to fix. > getListing wrongly associates Erasure Coding

[jira] [Updated] (HDFS-9047) Retire libwebhdfs

[ https://issues.apache.org/jira/browse/HDFS-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai updated HDFS-9047: - Release Note: libwebhdfs has been retired in 2.8.0 due to the lack of maintenance. > Retire libwebhdfs >

[jira] [Commented] (HDFS-9607) Advance Hadoop Architecture (AHA) - HDFS

[ https://issues.apache.org/jira/browse/HDFS-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086539#comment-15086539 ] Dinesh S. Atreya commented on HDFS-9607: Copying [comment |

[jira] [Updated] (HDFS-9047) Retire libwebhdfs

[ https://issues.apache.org/jira/browse/HDFS-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai updated HDFS-9047: - Resolution: Fixed Hadoop Flags: Reviewed,Incompatible change Fix Version/s: 2.8.0

[jira] [Updated] (HDFS-9313) Possible NullPointerException in BlockManager if no excess replica can be chosen

[ https://issues.apache.org/jira/browse/HDFS-9313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HDFS-9313: - Target Version/s: 2.6.4 > Possible NullPointerException in BlockManager if no excess replica can be >

[jira] [Updated] (HDFS-9047) Retire libwebhdfs

[ https://issues.apache.org/jira/browse/HDFS-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai updated HDFS-9047: - Target Version/s: (was: 3.0.0) > Retire libwebhdfs > - > > Key:

[jira] [Commented] (HDFS-9047) Retire libwebhdfs

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

[jira] [Created] (HDFS-9622) get Block Locations is always unstable

lichao liu created HDFS-9622: Summary: get Block Locations is always unstable Key: HDFS-9622 URL: https://issues.apache.org/jira/browse/HDFS-9622 Project: Hadoop HDFS Issue Type: Bug Affects

[jira] [Commented] (HDFS-9621) getListing wrongly associates Erasure Coding policy to pre-existing replicated files under an EC directory

[ https://issues.apache.org/jira/browse/HDFS-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086760#comment-15086760 ] Kai Zheng commented on HDFS-9621: - Thanks for the work Jing. The patch looks great. Some minor comments: 1.

[jira] [Commented] (HDFS-9600) do not check replication if the block is under construction

[ https://issues.apache.org/jira/browse/HDFS-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086858#comment-15086858 ] Vinayakumar B commented on HDFS-9600: - bq. The native build fails when libwebhdfs in contrib is built.

[jira] [Commented] (HDFS-9047) Retire libwebhdfs

[ https://issues.apache.org/jira/browse/HDFS-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086600#comment-15086600 ] Junping Du commented on HDFS-9047: -- Hi [~wheat9], what's the plan for branch-2.6/2.7? Remove it or fix it?

[jira] [Updated] (HDFS-9620) Slow writer may fail permanently if pipeline breaks.

[ https://issues.apache.org/jira/browse/HDFS-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-9620: -- Component/s: security hdfs-client > Slow writer may fail permanently if

[jira] [Created] (HDFS-9623) Update example configuration of block state change log in log4j.properties

Masatake Iwasaki created HDFS-9623: -- Summary: Update example configuration of block state change log in log4j.properties Key: HDFS-9623 URL: https://issues.apache.org/jira/browse/HDFS-9623 Project:

[jira] [Commented] (HDFS-9607) Advance Hadoop Architecture (AHA) - HDFS

[ https://issues.apache.org/jira/browse/HDFS-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086662#comment-15086662 ] Dinesh S. Atreya commented on HDFS-9607: Both [~ste...@apache.org] and [~wheat9] have raised good

[jira] [Commented] (HDFS-9047) Retire libwebhdfs

[ https://issues.apache.org/jira/browse/HDFS-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086683#comment-15086683 ] Haohui Mai commented on HDFS-9047: -- Looks like there is no effort on fixing anything. IMO +1 on removing

[jira] [Comment Edited] (HDFS-9047) Retire libwebhdfs

[ https://issues.apache.org/jira/browse/HDFS-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086683#comment-15086683 ] Haohui Mai edited comment on HDFS-9047 at 1/7/16 2:25 AM: -- Looks like there is no

[jira] [Commented] (HDFS-9621) getListing wrongly associates Erasure Coding policy to pre-existing replicated files under an EC directory

[ https://issues.apache.org/jira/browse/HDFS-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086707#comment-15086707 ] Hadoop QA commented on HDFS-9621: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (HDFS-9623) Update example configuration of block state change log in log4j.properties

[ https://issues.apache.org/jira/browse/HDFS-9623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki updated HDFS-9623: --- Attachment: HDFS-9623.001.patch > Update example configuration of block state change log in

[jira] [Commented] (HDFS-8891) HDFS concat should keep srcs order

[ https://issues.apache.org/jira/browse/HDFS-8891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086634#comment-15086634 ] Chris Douglas commented on HDFS-8891: - bq. shall we cherry-pick this fix to 2.6.4 as well? Yes, it

[jira] [Updated] (HDFS-9608) Disk IO imbalance in HDFS with heterogeneous storages

[ https://issues.apache.org/jira/browse/HDFS-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou updated HDFS-9608: --- Description: Currently RoundRobinVolumeChoosingPolicy use a shared index to choose volumes in HDFS with

[jira] [Commented] (HDFS-9600) do not check replication if the block is under construction

[ https://issues.apache.org/jira/browse/HDFS-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086911#comment-15086911 ] Vinayakumar B commented on HDFS-9600: - Committed to trunk, branch-2, branch-2.7 and branch-2.6 Thanks

[jira] [Updated] (HDFS-9608) Disk IO imbalance in HDFS with heterogeneous storages

[ https://issues.apache.org/jira/browse/HDFS-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou updated HDFS-9608: --- Description: Currently RoundRobinVolumeChoosingPolicy use a shared index to choose volumes in HDFS with

[jira] [Created] (HDFS-9624) DataNode start slowly due to the initial DU command operations

Lin Yiqun created HDFS-9624: --- Summary: DataNode start slowly due to the initial DU command operations Key: HDFS-9624 URL: https://issues.apache.org/jira/browse/HDFS-9624 Project: Hadoop HDFS

[jira] [Commented] (HDFS-8356) Document missing properties in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086939#comment-15086939 ] Ray Chiang commented on HDFS-8356: -- RE: Failing unit tests Different set than previous run and both tests

[jira] [Updated] (HDFS-9608) Disk IO imbalance in HDFS with heterogeneous storages

[ https://issues.apache.org/jira/browse/HDFS-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou updated HDFS-9608: --- Attachment: HDFS-9608.02.patch Thanks Kai for the helpful suggestions! Modifications made to the previous

[jira] [Updated] (HDFS-9624) DataNode start slowly due to the initial DU command operations

[ https://issues.apache.org/jira/browse/HDFS-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated HDFS-9624: Attachment: HDFS-9624.001.patch > DataNode start slowly due to the initial DU command operations >

[jira] [Commented] (HDFS-9600) do not check replication if the block is under construction

[ https://issues.apache.org/jira/browse/HDFS-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086927#comment-15086927 ] Vinayakumar B commented on HDFS-9600: - Merged to branch-2.8 as well. > do not check replication if the

[jira] [Commented] (HDFS-9619) DataNode sometimes can not find blockpool for the correct namenode

[ https://issues.apache.org/jira/browse/HDFS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086225#comment-15086225 ] Hadoop QA commented on HDFS-9619: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Created] (HDFS-9620) Slow writer may fail permanently if pipeline breaks.

Kihwal Lee created HDFS-9620: Summary: Slow writer may fail permanently if pipeline breaks. Key: HDFS-9620 URL: https://issues.apache.org/jira/browse/HDFS-9620 Project: Hadoop HDFS Issue Type:

[jira] [Commented] (HDFS-9620) Slow writer may fail permanently if pipeline breaks.

[ https://issues.apache.org/jira/browse/HDFS-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086340#comment-15086340 ] Kihwal Lee commented on HDFS-9620: -- The read path already has a mechanism for refetching block tokens, but

  1   2   >