[jira] [Commented] (HDFS-14997) BPServiceActor processes commands from NameNode asynchronously

[ https://issues.apache.org/jira/browse/HDFS-14997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418516#comment-17418516 ] Xiaoqiao He commented on HDFS-14997: cherry-pick to branch-3.2 and branch-3.2.3. > BPServiceActor

[jira] [Updated] (HDFS-14997) BPServiceActor processes commands from NameNode asynchronously

[ https://issues.apache.org/jira/browse/HDFS-14997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14997: --- Fix Version/s: 3.2.3 > BPServiceActor processes commands from NameNode asynchronously >

[jira] [Updated] (HDFS-15113) Missing IBR when NameNode restart if open processCommand async feature

[ https://issues.apache.org/jira/browse/HDFS-15113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15113: --- Fix Version/s: 3.2.4 > Missing IBR when NameNode restart if open processCommand async feature >

[jira] [Commented] (HDFS-15113) Missing IBR when NameNode restart if open processCommand async feature

[ https://issues.apache.org/jira/browse/HDFS-15113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17416727#comment-17416727 ] Xiaoqiao He commented on HDFS-15113: Cherry-pick to branch-3.2. > Missing IBR when NameNode restart

[jira] [Commented] (HDFS-15075) Remove process command timing from BPServiceActor

[ https://issues.apache.org/jira/browse/HDFS-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17416724#comment-17416724 ] Xiaoqiao He commented on HDFS-15075: Cherry-pick to branch-3.2 > Remove process command timing from

[jira] [Commented] (HDFS-15651) Client could not obtain block when DN CommandProcessingThread exit

[ https://issues.apache.org/jira/browse/HDFS-15651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17416725#comment-17416725 ] Xiaoqiao He commented on HDFS-15651: Cherry-pick to branch-3.2. > Client could not obtain block when

[jira] [Updated] (HDFS-15651) Client could not obtain block when DN CommandProcessingThread exit

[ https://issues.apache.org/jira/browse/HDFS-15651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15651: --- Fix Version/s: 3.2.4 > Client could not obtain block when DN CommandProcessingThread exit >

[jira] [Updated] (HDFS-15075) Remove process command timing from BPServiceActor

[ https://issues.apache.org/jira/browse/HDFS-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15075: --- Fix Version/s: 3.2.4 > Remove process command timing from BPServiceActor >

[jira] [Commented] (HDFS-14997) BPServiceActor processes commands from NameNode asynchronously

[ https://issues.apache.org/jira/browse/HDFS-14997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17416722#comment-17416722 ] Xiaoqiao He commented on HDFS-14997: [~brahmareddy] This patch is ready now, less conflict and verify

[jira] [Updated] (HDFS-14997) BPServiceActor processes commands from NameNode asynchronously

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

[jira] [Commented] (HDFS-14997) BPServiceActor processes commands from NameNode asynchronously

[ https://issues.apache.org/jira/browse/HDFS-14997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17416630#comment-17416630 ] Xiaoqiao He commented on HDFS-14997: Failed unit tests seems not related to this changes. Will commit

[jira] [Reopened] (HDFS-14997) BPServiceActor processes commands from NameNode asynchronously

[ https://issues.apache.org/jira/browse/HDFS-14997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reopened HDFS-14997: > BPServiceActor processes commands from NameNode asynchronously >

[jira] [Updated] (HDFS-14997) BPServiceActor processes commands from NameNode asynchronously

[ https://issues.apache.org/jira/browse/HDFS-14997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14997: --- Attachment: HDFS-14997-branch-3.2.001.patch Status: Patch Available (was: Reopened) submit

[jira] [Commented] (HDFS-15160) ReplicaMap, Disk Balancer, Directory Scanner and various FsDatasetImpl methods should use datanode readlock

[ https://issues.apache.org/jira/browse/HDFS-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17414794#comment-17414794 ] Xiaoqiao He commented on HDFS-15160: Thanks [~brahmareddy] for your information. I have cherry-pick

[jira] [Updated] (HDFS-15150) Introduce read write lock to Datanode

[ https://issues.apache.org/jira/browse/HDFS-15150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15150: --- Fix Version/s: 3.2.4 > Introduce read write lock to Datanode > -

[jira] [Updated] (HDFS-15818) Fix TestFsDatasetImpl.testReadLockCanBeDisabledByConfig

[ https://issues.apache.org/jira/browse/HDFS-15818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15818: --- Fix Version/s: 3.2.4 > Fix TestFsDatasetImpl.testReadLockCanBeDisabledByConfig >

[jira] [Updated] (HDFS-15457) TestFsDatasetImpl fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15457: --- Fix Version/s: 3.2.4 > TestFsDatasetImpl fails intermittently >

[jira] [Updated] (HDFS-15160) ReplicaMap, Disk Balancer, Directory Scanner and various FsDatasetImpl methods should use datanode readlock

[ https://issues.apache.org/jira/browse/HDFS-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15160: --- Fix Version/s: 3.2.3 > ReplicaMap, Disk Balancer, Directory Scanner and various FsDatasetImpl >

[jira] [Resolved] (HDFS-16223) AvailableSpaceRackFaultTolerantBlockPlacementPolicy should use chooseRandomWithStorageTypeTwoTrial() for better performance.

[ https://issues.apache.org/jira/browse/HDFS-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16223. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk.

[jira] [Updated] (HDFS-15818) Fix TestFsDatasetImpl.testReadLockCanBeDisabledByConfig

[ https://issues.apache.org/jira/browse/HDFS-15818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15818: --- Fix Version/s: 3.2.3 > Fix TestFsDatasetImpl.testReadLockCanBeDisabledByConfig >

[jira] [Updated] (HDFS-15457) TestFsDatasetImpl fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15457: --- Fix Version/s: 3.2.3 > TestFsDatasetImpl fails intermittently >

[jira] [Updated] (HDFS-15150) Introduce read write lock to Datanode

[ https://issues.apache.org/jira/browse/HDFS-15150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15150: --- Fix Version/s: 3.2.3 > Introduce read write lock to Datanode > -

[jira] [Resolved] (HDFS-15160) ReplicaMap, Disk Balancer, Directory Scanner and various FsDatasetImpl methods should use datanode readlock

[ https://issues.apache.org/jira/browse/HDFS-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-15160. Fix Version/s: 3.2.3 Resolution: Fixed > ReplicaMap, Disk Balancer, Directory Scanner and

[jira] [Commented] (HDFS-16196) Namesystem#completeFile method will log incorrect path information when router to access

[ https://issues.apache.org/jira/browse/HDFS-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17410484#comment-17410484 ] Xiaoqiao He commented on HDFS-16196: Thanks [~lei w] for your report. It is confused log for users. I

[jira] [Commented] (HDFS-16200) Improve NameNode failover

[ https://issues.apache.org/jira/browse/HDFS-16200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17410148#comment-17410148 ] Xiaoqiao He commented on HDFS-16200: Thanks [~aihuaxu] for your report. I think the best way is to

[jira] [Commented] (HDFS-16196) Namesystem#completeFile method will log incorrect path information when router to access

[ https://issues.apache.org/jira/browse/HDFS-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17410147#comment-17410147 ] Xiaoqiao He commented on HDFS-16196: [~lei w], Thanks for you report. Which version do you deploy?

[jira] [Updated] (HDFS-16044) Fix getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16044: --- Attachment: HDFS-16044.05.patch Hadoop Flags: (was: Reviewed) Affects

[jira] [Updated] (HDFS-16138) BlockReportProcessingThread exit doesn't print the actual stack

[ https://issues.apache.org/jira/browse/HDFS-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16138: --- Issue Type: Improvement (was: Bug) > BlockReportProcessingThread exit doesn't print the actual

[jira] [Resolved] (HDFS-16138) BlockReportProcessingThread exit doesn't print the actual stack

[ https://issues.apache.org/jira/browse/HDFS-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16138. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed Thanks [~prasad-acit]

[jira] [Updated] (HDFS-16138) BlockReportProcessingThread exit doesn't print the actual stack

[ https://issues.apache.org/jira/browse/HDFS-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16138: --- Summary: BlockReportProcessingThread exit doesn't print the actual stack (was:

[jira] [Resolved] (HDFS-16194) Simplify the code with DatanodeID#getXferAddrWithHostname

[ https://issues.apache.org/jira/browse/HDFS-16194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16194. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk.

[jira] [Comment Edited] (HDFS-16155) Allow configurable exponential backoff in DFSInputStream refetchLocations

[ https://issues.apache.org/jira/browse/HDFS-16155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395135#comment-17395135 ] Xiaoqiao He edited comment on HDFS-16155 at 8/7/21, 7:00 AM: - Thanks

[jira] [Commented] (HDFS-16155) Allow configurable exponential backoff in DFSInputStream refetchLocations

[ https://issues.apache.org/jira/browse/HDFS-16155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395135#comment-17395135 ] Xiaoqiao He commented on HDFS-16155: Thanks [~bbeaudreault] for your report and works. Add to

[jira] [Assigned] (HDFS-16155) Allow configurable exponential backoff in DFSInputStream refetchLocations

[ https://issues.apache.org/jira/browse/HDFS-16155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-16155: -- Assignee: Bryan Beaudreault > Allow configurable exponential backoff in DFSInputStream

[jira] [Updated] (HDFS-16146) All three replicas are lost due to not adding a new DataNode in time

[ https://issues.apache.org/jira/browse/HDFS-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16146: --- Component/s: (was: hdfs) (was: datanode) dfsclient > All

[jira] [Updated] (HDFS-16146) All three replicas are lost due to not adding a new DataNode in time

[ https://issues.apache.org/jira/browse/HDFS-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16146: --- Issue Type: Improvement (was: Bug) > All three replicas are lost due to not adding a new DataNode

[jira] [Resolved] (HDFS-16146) All three replicas are lost due to not adding a new DataNode in time

[ https://issues.apache.org/jira/browse/HDFS-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16146. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk.

[jira] [Commented] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

[ https://issues.apache.org/jira/browse/HDFS-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389820#comment-17389820 ] Xiaoqiao He commented on HDFS-15175: Thanks [~sodonnell] for your reminder. cherry-pick-ed to

[jira] [Updated] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

[ https://issues.apache.org/jira/browse/HDFS-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15175: --- Fix Version/s: 3.3.2 > Multiple CloseOp shared block instance causes the standby namenode to crash

[jira] [Commented] (HDFS-16146) All three replicas are lost due to not adding a new DataNode in time

[ https://issues.apache.org/jira/browse/HDFS-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389769#comment-17389769 ] Xiaoqiao He commented on HDFS-16146: Great catch here! LGTM. Thanks [~zhangshuyan] for your report

[jira] [Comment Edited] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

[ https://issues.apache.org/jira/browse/HDFS-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389232#comment-17389232 ] Xiaoqiao He edited comment on HDFS-15175 at 7/29/21, 3:30 AM: -- Backport to

[jira] [Commented] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

[ https://issues.apache.org/jira/browse/HDFS-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389232#comment-17389232 ] Xiaoqiao He commented on HDFS-15175: Backport to branch-3.2 first considering 3.2.3 is pending

[jira] [Updated] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

[ https://issues.apache.org/jira/browse/HDFS-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15175: --- Fix Version/s: 3.2.4 3.2.3 > Multiple CloseOp shared block instance causes the

[jira] [Comment Edited] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

[ https://issues.apache.org/jira/browse/HDFS-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389225#comment-17389225 ] Xiaoqiao He edited comment on HDFS-15175 at 7/29/21, 3:23 AM: -- Committed to

[jira] [Updated] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

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

[jira] [Commented] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

[ https://issues.apache.org/jira/browse/HDFS-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388639#comment-17388639 ] Xiaoqiao He commented on HDFS-15175: LGTM. +1. > Multiple CloseOp shared block instance causes the

[jira] [Updated] (HDFS-16022) matlab mapreduce v95 demos can't run hadoop-3.2.2 run time

[ https://issues.apache.org/jira/browse/HDFS-16022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16022: --- Target Version/s: 3.2.4 (was: 3.2.2) ===Bulk update=== planning to cut the branch for Hadoop 3.2.3

[jira] [Updated] (HDFS-15289) Allow viewfs mounts with HDFS/HCFS scheme and centralized mount table

[ https://issues.apache.org/jira/browse/HDFS-15289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15289: --- Target Version/s: 3.4.0, 3.3.2, 3.2.4 (was: 3.4.0, 3.2.3, 3.3.2) ===Bulk update=== planning to cut

[jira] [Updated] (HDFS-16014) Issue in checking native pmdk lib by 'hadoop checknative' command

[ https://issues.apache.org/jira/browse/HDFS-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16014: --- Target Version/s: 3.4.0, 3.2.4 (was: 3.4.0, 3.2.3) ===Bulk update=== planning to cut the branch

[jira] [Updated] (HDFS-16139) Update BPServiceActor Scheduler's nextBlockReportTime atomically

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

[jira] [Resolved] (HDFS-16131) Show storage type for failed volumes on namenode web

[ https://issues.apache.org/jira/browse/HDFS-16131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16131. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk.

[jira] [Commented] (HDFS-16139) Update BPServiceActor Scheduler's nextBlockReportTime atomically

[ https://issues.apache.org/jira/browse/HDFS-16139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386833#comment-17386833 ] Xiaoqiao He commented on HDFS-16139: Make sense to me. +1 from my side. > Update BPServiceActor

[jira] [Commented] (HDFS-16118) Improve the number of handlers that initialize NameNodeRpcServer#clientRpcServer

[ https://issues.apache.org/jira/browse/HDFS-16118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386831#comment-17386831 ] Xiaoqiao He commented on HDFS-16118: Thanks [~jianghuazhu] involve me here. IMO it is not necessary

[jira] [Commented] (HDFS-16134) Optimize RPC throughput

[ https://issues.apache.org/jira/browse/HDFS-16134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386828#comment-17386828 ] Xiaoqiao He commented on HDFS-16134: Thanks [~jianghuazhu] involve me here. HDFS-15486, HDFS-15869

[jira] [Assigned] (HDFS-16134) Optimize RPC throughput

[ https://issues.apache.org/jira/browse/HDFS-16134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-16134: -- Assignee: JiangHua Zhu > Optimize RPC throughput > --- > >

[jira] [Commented] (HDFS-16137) Improve the comments related to FairCallQueue#queues

[ https://issues.apache.org/jira/browse/HDFS-16137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386825#comment-17386825 ] Xiaoqiao He commented on HDFS-16137: +1. Thanks. > Improve the comments related to

[jira] [Commented] (HDFS-16138) BlockReportProcessingThread exit doesnt print the acutal stack

[ https://issues.apache.org/jira/browse/HDFS-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386824#comment-17386824 ] Xiaoqiao He commented on HDFS-16138: Thanks [~prasad-acit] involve me here. Which version do you

[jira] [Commented] (HDFS-16139) Update BPServiceActor Scheduler's nextBlockReportTime atomically

[ https://issues.apache.org/jira/browse/HDFS-16139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386822#comment-17386822 ] Xiaoqiao He commented on HDFS-16139: Thanks [~vjasani] for your report and contributions.

[jira] [Assigned] (HDFS-16087) RBF balance process is stuck at DisableWrite stage

[ https://issues.apache.org/jira/browse/HDFS-16087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-16087: -- Assignee: Eric Yin > RBF balance process is stuck at DisableWrite stage >

[jira] [Resolved] (HDFS-16087) RBF balance process is stuck at DisableWrite stage

[ https://issues.apache.org/jira/browse/HDFS-16087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16087. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk.

[jira] [Commented] (HDFS-15942) Increase Quota initialization threads

[ https://issues.apache.org/jira/browse/HDFS-15942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383264#comment-17383264 ] Xiaoqiao He commented on HDFS-15942: cherry-pick to branch-3.2. > Increase Quota initialization

[jira] [Updated] (HDFS-15942) Increase Quota initialization threads

[ https://issues.apache.org/jira/browse/HDFS-15942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15942: --- Fix Version/s: 3.2.3 > Increase Quota initialization threads > -

[jira] [Commented] (HDFS-15651) Client could not obtain block when DN CommandProcessingThread exit

[ https://issues.apache.org/jira/browse/HDFS-15651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383261#comment-17383261 ] Xiaoqiao He commented on HDFS-15651: Thanks [~hemanthboyina] for your information. I just found that

[jira] [Updated] (HDFS-16067) Support Append API in NNThroughputBenchmark

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

[jira] [Commented] (HDFS-16067) Support Append API in NNThroughputBenchmark

[ https://issues.apache.org/jira/browse/HDFS-16067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381178#comment-17381178 ] Xiaoqiao He commented on HDFS-16067: Thanks [~prasad-acit] for your update. {code:java} } + /**

[jira] [Commented] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376556#comment-17376556 ] Xiaoqiao He commented on HDFS-16115: I agree with you that HDFS-15651 is rough solution for this

[jira] [Commented] (HDFS-16100) HA: Improve performance of Standby node transition to Active

[ https://issues.apache.org/jira/browse/HDFS-16100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376251#comment-17376251 ] Xiaoqiao He commented on HDFS-16100: [^HDFS-16100.001.patch] it is safe to checkin and improve it for

[jira] [Commented] (HDFS-16095) Add lsQuotaList command and getQuotaListing api for hdfs quota

[ https://issues.apache.org/jira/browse/HDFS-16095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375756#comment-17375756 ] Xiaoqiao He commented on HDFS-16095: [~zhuxiangyi] Thanks for involving me here. {quote}It has a

[jira] [Commented] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375741#comment-17375741 ] Xiaoqiao He commented on HDFS-16115: [~Daniel Ma] Thanks for your report. I am not sure if HDFS-15651

[jira] [Commented] (HDFS-16100) HA: Improve performance of Standby node transition to Active

[ https://issues.apache.org/jira/browse/HDFS-16100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17374323#comment-17374323 ] Xiaoqiao He commented on HDFS-16100: Thanks [~ayushtkn] for your comments. IMO, it is safe to to

[jira] [Commented] (HDFS-16100) HA: Improve performance of Standby node transition to Active

[ https://issues.apache.org/jira/browse/HDFS-16100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372912#comment-17372912 ] Xiaoqiao He commented on HDFS-16100: I am not familiar to this logic, but it sounds reasonable at

[jira] [Resolved] (HDFS-16099) Make bpServiceToActive to be volatile

[ https://issues.apache.org/jira/browse/HDFS-16099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16099. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk.

[jira] [Commented] (HDFS-16088) Standby NameNode process getLiveDatanodeStorageReport request to reduce Active load

[ https://issues.apache.org/jira/browse/HDFS-16088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372119#comment-17372119 ] Xiaoqiao He commented on HDFS-16088: Thanks [~tomscut] involve me here. It makes sense to me at first

[jira] [Commented] (HDFS-16093) DataNodes under decommission will still be returned to the client via getLocatedBlocks, so the client may request decommissioning datanodes to read which will cause bad

[ https://issues.apache.org/jira/browse/HDFS-16093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372116#comment-17372116 ] Xiaoqiao He commented on HDFS-16093: -1 to remove DECOMMISSIONING state node from `LocatedBlocks`

[jira] [Commented] (HDFS-16102) Remove redundant iteration in BlockManager#removeBlocksAssociatedTo(...) to save time

[ https://issues.apache.org/jira/browse/HDFS-16102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372114#comment-17372114 ] Xiaoqiao He commented on HDFS-16102: Thanks [~lei w] for your report, It seems that your codebase is

[jira] [Commented] (HDFS-16097) Datanode receives ipc requests will throw NPE when datanode quickly restart

[ https://issues.apache.org/jira/browse/HDFS-16097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372105#comment-17372105 ] Xiaoqiao He commented on HDFS-16097: Thanks [~lei w] for your report. It is good improvement! Do you

[jira] [Updated] (HDFS-16097) Datanode receives ipc requests will throw NPE when datanode quickly restart

[ https://issues.apache.org/jira/browse/HDFS-16097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16097: --- Status: Patch Available (was: Open) > Datanode receives ipc requests will throw NPE when datanode

[jira] [Assigned] (HDFS-16097) Datanode receives ipc requests will throw NPE when datanode quickly restart

[ https://issues.apache.org/jira/browse/HDFS-16097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-16097: -- Assignee: lei w > Datanode receives ipc requests will throw NPE when datanode quickly restart

[jira] [Commented] (HDFS-16100) HA: Improve performance of Standby node transition to Active

[ https://issues.apache.org/jira/browse/HDFS-16100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372103#comment-17372103 ] Xiaoqiao He commented on HDFS-16100: Thanks [~g20141821] for your report. Add [~g20141821] to

[jira] [Assigned] (HDFS-16100) HA: Improve performance of Standby node transition to Active

[ https://issues.apache.org/jira/browse/HDFS-16100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-16100: -- Assignee: wudeyu > HA: Improve performance of Standby node transition to Active >

[jira] [Commented] (HDFS-16067) Support Append API in NNThroughputBenchmark

[ https://issues.apache.org/jira/browse/HDFS-16067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369515#comment-17369515 ] Xiaoqiao He commented on HDFS-16067: Most of failed unit tests is related with

[jira] [Updated] (HDFS-16044) Fix getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16044: --- Fix Version/s: (was: 3.4.0) > Fix getListing call getLocatedBlocks even source is a directory >

[jira] [Reopened] (HDFS-16044) Fix getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reopened HDFS-16044: > Fix getListing call getLocatedBlocks even source is a directory >

[jira] [Commented] (HDFS-16044) Fix getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369506#comment-17369506 ] Xiaoqiao He commented on HDFS-16044: This PR seems broken unit test but not reported at the last

[jira] [Updated] (HDFS-16044) Fix getListing call getLocatedBlocks even source is a directory

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

[jira] [Updated] (HDFS-16044) Fix getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16044: --- Summary: Fix getListing call getLocatedBlocks even source is a directory (was: getListing call

[jira] [Commented] (HDFS-16067) Support Append API in NNThroughputBenchmark

[ https://issues.apache.org/jira/browse/HDFS-16067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17368932#comment-17368932 ] Xiaoqiao He commented on HDFS-16067: Try to check failed unit tests at local, both of them works fine

[jira] [Commented] (HDFS-16044) getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367419#comment-17367419 ] Xiaoqiao He commented on HDFS-16044: [^HDFS-16044.03.patch] LGTM. +1 from my side. cc

[jira] [Commented] (HDFS-16044) getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366728#comment-17366728 ] Xiaoqiao He commented on HDFS-16044: Please check report by Yetus, include checkstyle and failed unit

[jira] [Commented] (HDFS-16067) Support Append API in NNThroughputBenchmark

[ https://issues.apache.org/jira/browse/HDFS-16067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366727#comment-17366727 ] Xiaoqiao He commented on HDFS-16067: Thanks [~prasad-acit] for your update. {quote}A. Regarding

[jira] [Updated] (HDFS-14575) LeaseRenewer#daemon threads leak in DFSClient

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

[jira] [Commented] (HDFS-16067) Support Append API in NNThroughputBenchmark

[ https://issues.apache.org/jira/browse/HDFS-16067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366167#comment-17366167 ] Xiaoqiao He commented on HDFS-16067: Thanks [~prasad-acit] involve me here. I agree that it is useful

[jira] [Commented] (HDFS-14575) LeaseRenewer#daemon threads leak in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-14575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366103#comment-17366103 ] Xiaoqiao He commented on HDFS-14575: +1 on [^HDFS-14575.004.patch]. Will commit to trunk shortly if

[jira] [Commented] (HDFS-14575) LeaseRenewer#daemon threads leak in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-14575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365916#comment-17365916 ] Xiaoqiao He commented on HDFS-14575: Thanks [~prasad-acit] for your works here. Please fix the

[jira] [Commented] (HDFS-16044) getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365894#comment-17365894 ] Xiaoqiao He commented on HDFS-16044: [~pilchard] Thanks for your update. The core improvement seems

[jira] [Commented] (HDFS-16044) getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355605#comment-17355605 ] Xiaoqiao He commented on HDFS-16044: {quote}IMO, unless it's a regression only in 3.3.1 or 3.3.0, we

[jira] [Commented] (HDFS-16044) getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355584#comment-17355584 ] Xiaoqiao He commented on HDFS-16044: It seems that both branch-3.1/3.2/3.3/trunk branches has

[jira] [Commented] (HDFS-16044) getListing call getLocatedBlocks even source is a directory

[ https://issues.apache.org/jira/browse/HDFS-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355123#comment-17355123 ] Xiaoqiao He commented on HDFS-16044: [~pilchard] Thanks for your report. Would you mind to offer

[jira] [Resolved] (HDFS-15998) Fix NullPointException In listOpenFiles

[ https://issues.apache.org/jira/browse/HDFS-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-15998. Fix Version/s: 3.3.2 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed

[jira] [Commented] (HDFS-16043) HDFS : Delete performance optimization

[ https://issues.apache.org/jira/browse/HDFS-16043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355104#comment-17355104 ] Xiaoqiao He commented on HDFS-16043: Thanks [~zhuxiangyi] for your works. It is interesting

<    1   2   3   4   5   6   7   8   9   10   >