[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&focusedCommentId=17388639#comment-17388639 ] Xiaoqiao He commented on HDFS-15175: LGTM. +1. > Multiple CloseOp shared block insta

[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] [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&focusedCommentId=17389225#comment-17389225 ] Xiaoqiao He edited comment on HDFS-15175 at 7/29/21, 3:23 AM: -

[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 sta

[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&focusedCommentId=17389232#comment-17389232 ] Xiaoqiao He commented on HDFS-15175: Backport to branch-3.2 first considering 3.2.3 i

[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&focusedCommentId=17389232#comment-17389232 ] Xiaoqiao He edited comment on HDFS-15175 at 7/29/21, 3:30 AM: -

[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&focusedCommentId=17389769#comment-17389769 ] Xiaoqiao He commented on HDFS-16146: Great catch here! LGTM. Thanks [~zhangshuyan] fo

[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-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&focusedCommentId=17389820#comment-17389820 ] Xiaoqiao He commented on HDFS-15175: Thanks [~sodonnell] for your reminder. cherry-pi

[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 in

[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. Thank

[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 th

[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 refetch

[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&focusedCommentId=17395135#comment-17395135 ] Xiaoqiao He commented on HDFS-16155: Thanks [~bbeaudreault] for your report and works

[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&focusedCommentId=17395135#comment-17395135 ] Xiaoqiao He edited comment on HDFS-16155 at 8/7/21, 7:00 AM: -

[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. Thank

[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: BlockReportProcessing

[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 stack

[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] for

[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 Version/s:

[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&focusedCommentId=17410147#comment-17410147 ] Xiaoqiao He commented on HDFS-16196: [~lei w], Thanks for you report. Which version d

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

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

[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&focusedCommentId=17410484#comment-17410484 ] Xiaoqiao He commented on HDFS-16196: Thanks [~lei w] for your report. It is confused

[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 va

[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] [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] [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. Thank

[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 > meth

[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-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] [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&focusedCommentId=17414794#comment-17414794 ] Xiaoqiao He commented on HDFS-15160: Thanks [~brahmareddy] for your information. I ha

[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 p

[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] [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&focusedCommentId=17416630#comment-17416630 ] Xiaoqiao He commented on HDFS-14997: Failed unit tests seems not related to this chan

[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) > B

[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&focusedCommentId=17416722#comment-17416722 ] Xiaoqiao He commented on HDFS-14997: [~brahmareddy] This patch is ready now, less con

[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] [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] [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&focusedCommentId=17416725#comment-17416725 ] Xiaoqiao He commented on HDFS-15651: Cherry-pick to branch-3.2. > Client could not o

[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&focusedCommentId=17416724#comment-17416724 ] Xiaoqiao He commented on HDFS-15075: Cherry-pick to branch-3.2 > Remove process comm

[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&focusedCommentId=17416727#comment-17416727 ] Xiaoqiao He commented on HDFS-15113: Cherry-pick to branch-3.2. > Missing IBR when N

[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] [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] [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&focusedCommentId=17418516#comment-17418516 ] Xiaoqiao He commented on HDFS-14997: cherry-pick to branch-3.2 and branch-3.2.3. > B

[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.3 cherry-pick to branch-3.2.3. > Remove process command timing from BPServiceActo

[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.3 cherry-pick to branch-3.2.3. > Client could not obtain block when DN CommandPro

[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.3 cherry-pick to branch-3.2.3. > Missing IBR when NameNode restart if open proces

[jira] [Commented] (HDFS-16235) Deadlock in LeaseRenewer for static remove method

[ https://issues.apache.org/jira/browse/HDFS-16235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422054#comment-17422054 ] Xiaoqiao He commented on HDFS-16235: Cherry-pick to branch-3.3 and branch-3.2(include

[jira] [Updated] (HDFS-16235) Deadlock in LeaseRenewer for static remove method

[ https://issues.apache.org/jira/browse/HDFS-16235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16235: --- Fix Version/s: 3.2.4 3.3.2 3.2.3 > Deadlock in LeaseRenewer for

[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&focusedCommentId=17422055#comment-17422055 ] Xiaoqiao He commented on HDFS-14575: Thanks for reminder. Cherry-pick to branch-3.3 a

[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.2.4 3.3.2 3.2.3 > LeaseRenewer#daemon threads

[jira] [Commented] (HDFS-16322) The NameNode implementation of ClientProtocol.truncate(...) can cause data loss.

[ https://issues.apache.org/jira/browse/HDFS-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443263#comment-17443263 ] Xiaoqiao He commented on HDFS-16322: Thanks [~Nsupyq] for your report. It is interest

[jira] [Commented] (HDFS-16320) Datanode retrieve slownode information from NameNode

[ https://issues.apache.org/jira/browse/HDFS-16320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443268#comment-17443268 ] Xiaoqiao He commented on HDFS-16320: Thanks [~Symious] for your report and patch. IMO

[jira] [Commented] (HDFS-16318) Add exception blockinfo

[ https://issues.apache.org/jira/browse/HDFS-16318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443273#comment-17443273 ] Xiaoqiao He commented on HDFS-16318: [~philipse] would you mind to add some informati

[jira] [Commented] (HDFS-16320) Datanode retrieve slownode information from NameNode

[ https://issues.apache.org/jira/browse/HDFS-16320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443283#comment-17443283 ] Xiaoqiao He commented on HDFS-16320: Thanks [~Symious] for your quick response. It is

[jira] [Commented] (HDFS-16322) The NameNode implementation of ClientProtocol.truncate(...) can cause data loss.

[ https://issues.apache.org/jira/browse/HDFS-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443550#comment-17443550 ] Xiaoqiao He commented on HDFS-16322: Thanks [~szetszwo] for your response. Considerin

[jira] [Commented] (HDFS-16322) The NameNode implementation of ClientProtocol.truncate(...) can cause data loss.

[ https://issues.apache.org/jira/browse/HDFS-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445627#comment-17445627 ] Xiaoqiao He commented on HDFS-16322: Great, it is graceful solution to enable RetryCa

[jira] [Resolved] (HDFS-16584) Record StandbyNameNode information when Balancer is running

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

[jira] [Updated] (HDFS-16588) Backport HDFS-16584 to branch-3.3.

[ https://issues.apache.org/jira/browse/HDFS-16588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16588: --- Summary: Backport HDFS-16584 to branch-3.3. (was: Backport HDFS-16584 to branch-3.3 and other active

[jira] [Resolved] (HDFS-16588) Backport HDFS-16584 to branch-3.3.

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

[jira] [Resolved] (HDFS-16627) Improve BPServiceActor#register log to add NameNode address

[ https://issues.apache.org/jira/browse/HDFS-16627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16627. Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk. Thanks [~slfan1989] for your con

[jira] [Updated] (HDFS-16627) Improve BPServiceActor#register log to add NameNode address

[ https://issues.apache.org/jira/browse/HDFS-16627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16627: --- Summary: Improve BPServiceActor#register log to add NameNode address (was: improve BPServiceActor#re

[jira] [Commented] (HDFS-16627) Improve BPServiceActor#register log to add NameNode address

[ https://issues.apache.org/jira/browse/HDFS-16627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553086#comment-17553086 ] Xiaoqiao He commented on HDFS-16627: [~slfan1989] BTW, the fix version label should b

[jira] [Resolved] (HDFS-16609) Fix Flakes Junit Tests that often report timeouts

[ https://issues.apache.org/jira/browse/HDFS-16609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16609. Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk. Thanks [~slfan1989]. > Fix Flak

[jira] [Updated] (HDFS-16598) Fix DataNode Fs

[ https://issues.apache.org/jira/browse/HDFS-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16598: --- Summary: Fix DataNode Fs (was: All datanodes [DatanodeInfoWithStorage[127.0.0.1:57448,DS-1b5f7e33-a2

[jira] [Updated] (HDFS-16598) Fix DataNode FsDatasetImpl lock issue without GS checks.

[ https://issues.apache.org/jira/browse/HDFS-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16598: --- Summary: Fix DataNode FsDatasetImpl lock issue without GS checks. (was: Fix DataNode Fs) > Fix Data

[jira] [Updated] (HDFS-16598) Fix DataNode FsDatasetImpl lock issue without GS checks.

[ https://issues.apache.org/jira/browse/HDFS-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16598: --- Parent: HDFS-15382 Issue Type: Sub-task (was: Bug) > Fix DataNode FsDatasetImpl lock issue w

[jira] [Resolved] (HDFS-16598) Fix DataNode FsDatasetImpl lock issue without GS checks.

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

[jira] [Updated] (HDFS-16628) RBF: Correct target directory when move to trash for kerberos login user.

[ https://issues.apache.org/jira/browse/HDFS-16628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16628: --- Summary: RBF: Correct target directory when move to trash for kerberos login user. (was: RBF: kerber

[jira] [Assigned] (HDFS-16628) RBF: Correct target directory when move to trash for kerberos login user.

[ https://issues.apache.org/jira/browse/HDFS-16628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-16628: -- Assignee: Xiping Zhang > RBF: Correct target directory when move to trash for kerberos login u

[jira] [Resolved] (HDFS-16628) RBF: Correct target directory when move to trash for kerberos login user.

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

[jira] [Updated] (HDFS-16600) Deadlock on DataNode

[ https://issues.apache.org/jira/browse/HDFS-16600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16600: --- Parent: HDFS-15382 Issue Type: Sub-task (was: Bug) > Deadlock on DataNode >

[jira] [Updated] (HDFS-16600) Fix deadlock of fine-grain lock for FsDatastImpl of DataNode.

[ https://issues.apache.org/jira/browse/HDFS-16600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16600: --- Summary: Fix deadlock of fine-grain lock for FsDatastImpl of DataNode. (was: Deadlock on DataNode)

[jira] [Resolved] (HDFS-16600) Fix deadlock of fine-grain lock for FsDatastImpl of DataNode.

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

[jira] [Commented] (HDFS-16600) Fix deadlock of fine-grain lock for FsDatastImpl of DataNode.

[ https://issues.apache.org/jira/browse/HDFS-16600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555638#comment-17555638 ] Xiaoqiao He commented on HDFS-16600: [~xuzq_zander] BTW, do you deploy this feature o

[jira] [Commented] (HDFS-15079) RBF: Client maybe get an unexpected result with network anomaly

[ https://issues.apache.org/jira/browse/HDFS-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561997#comment-17561997 ] Xiaoqiao He commented on HDFS-15079: [~xuzq_zander] Thanks to involve me here. I am n

[jira] [Commented] (HDFS-16657) Changing pool-level lock to volume-level lock for invalidation of blocks

[ https://issues.apache.org/jira/browse/HDFS-16657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566132#comment-17566132 ] Xiaoqiao He commented on HDFS-16657: [~yuanbo] Thanks for your proposal. IIRC, we has

[jira] [Resolved] (HDFS-16655) OIV: print out erasure coding policy name in oiv Delimited output

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

[jira] [Updated] (HDFS-16655) OIV: print out erasure coding policy name in oiv Delimited output

[ https://issues.apache.org/jira/browse/HDFS-16655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16655: --- Component/s: erasure-coding (was: tools) > OIV: print out erasure coding policy

[jira] [Resolved] (HDFS-16658) BlockManager should output some logs when logEveryBlock is true.

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

[jira] [Resolved] (HDFS-16704) Datanode return empty response instead of NPE for GetVolumeInfo during restarting

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

[jira] [Resolved] (HDFS-16717) Replace NPE with IOException in DataNode.class

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

[jira] [Resolved] (HDFS-16735) Reduce the number of HeartbeatManager loops

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

[jira] [Resolved] (HDFS-16593) Correct inaccurate BlocksRemoved metric on DataNode side

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

[jira] [Resolved] (HDFS-16781) setReplication方法不能设置整个目录的副本吗？whole folder?

[ https://issues.apache.org/jira/browse/HDFS-16781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16781. Resolution: Invalid [~zdltvxq] Thanks for your report. IIRC, setReplication api is kept for long t

[jira] [Updated] (HDFS-16781) setReplication方法不能设置整个目录的副本吗？whole folder?

[ https://issues.apache.org/jira/browse/HDFS-16781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16781: --- Priority: Minor (was: Blocker) > setReplication方法不能设置整个目录的副本吗？whole folder? > --

[jira] [Commented] (HDFS-16781) setReplication方法不能设置整个目录的副本吗？whole folder?

[ https://issues.apache.org/jira/browse/HDFS-16781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609358#comment-17609358 ] Xiaoqiao He commented on HDFS-16781: Great, welcome and look forwards to more discuss

[jira] [Updated] (HDFS-16798) SerialNumberMap should decrease current counter if the item exist

[ https://issues.apache.org/jira/browse/HDFS-16798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16798: --- Summary: SerialNumberMap should decrease current counter if the item exist (was: SerialNumberMap sho

[jira] [Resolved] (HDFS-16798) SerialNumberMap should decrease current counter if the item exist

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

[jira] [Updated] (HDFS-16783) Remove the redundant lock in deepCopyReplica

[ https://issues.apache.org/jira/browse/HDFS-16783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16783: --- Parent: HDFS-15382 Issue Type: Sub-task (was: Improvement) > Remove the redundant lock in de

[jira] [Updated] (HDFS-16783) Remove the redundant lock in deepCopyReplica and getFinalizedBlocks

[ https://issues.apache.org/jira/browse/HDFS-16783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16783: --- Summary: Remove the redundant lock in deepCopyReplica and getFinalizedBlocks (was: Remove the redund

[jira] [Resolved] (HDFS-16783) Remove the redundant lock in deepCopyReplica and getFinalizedBlocks

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

[jira] [Updated] (HDFS-16787) Remove the redundant lock in DataSetLockManager#removeLock.

[ https://issues.apache.org/jira/browse/HDFS-16787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16787: --- Summary: Remove the redundant lock in DataSetLockManager#removeLock. (was: Remove redundant lock in

[jira] [Updated] (HDFS-16787) Remove the redundant lock in DataSetLockManager#removeLock.

[ https://issues.apache.org/jira/browse/HDFS-16787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16787: --- Parent: HDFS-15382 Issue Type: Sub-task (was: Improvement) > Remove the redundant lock in Da

[jira] [Resolved] (HDFS-16787) Remove the redundant lock in DataSetLockManager#removeLock.

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

[jira] [Commented] (HDFS-10453) ReplicationMonitor thread could stuck for long time due to the race between replication and delete of same file in a large cluster.

[ https://issues.apache.org/jira/browse/HDFS-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624847#comment-17624847 ] Xiaoqiao He commented on HDFS-10453: [~yuyanlei] It works find in my internal cluster

[jira] [Commented] (HDFS-16836) StandbyCheckpointer can still trigger rollback fs image after RU is finalized

[ https://issues.apache.org/jira/browse/HDFS-16836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631431#comment-17631431 ] Xiaoqiao He commented on HDFS-16836: [~Lei Yang] Great catch and thanks for your repo

[jira] [Updated] (HDFS-16785) Avoid to hold write lock to improve performance when add volume.

[ https://issues.apache.org/jira/browse/HDFS-16785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16785: --- Summary: Avoid to hold write lock to improve performance when add volume. (was: DataNode hold BP wr

<    3   4   5   6   7   8   9   10   11   >