[jira] [Updated] (HDFS-16958) EC: Fix bug in processing EC excess redundancy

[ https://issues.apache.org/jira/browse/HDFS-16958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16958: --- Summary: EC: Fix bug in processing EC excess redundancy (was: Fix bug in processing EC excess redun

[jira] [Resolved] (HDFS-16948) Update log of BlockManager#chooseExcessRedundancyStriped when EC internal block is moved by balancer

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

[jira] [Resolved] (HDFS-16964) Improve processing of excess redundancy after failover

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

[jira] [Updated] (HDFS-16974) Consider volumes average load of each DataNode when choosing target.

[ https://issues.apache.org/jira/browse/HDFS-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16974: --- Summary: Consider volumes average load of each DataNode when choosing target. (was: Consider load of

[jira] [Resolved] (HDFS-16974) Consider volumes average load of each DataNode when choosing target.

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

[jira] [Resolved] (HDFS-16986) EC: Fix locationBudget in getListing()

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

[jira] [Resolved] (HDFS-16997) Set the locale to avoid printing useless logs in BlockSender

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

[jira] [Resolved] (HDFS-16999) Fix wrong use of processFirstBlockReport()

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

[jira] [Commented] (HDFS-17003) Erasure coding: invalidate wrong block after reporting bad blocks from datanode

[ https://issues.apache.org/jira/browse/HDFS-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720752#comment-17720752 ] Xiaoqiao He commented on HDFS-17003: [~zhanghaobo] Thanks for your report. Any more i

[jira] [Updated] (HDFS-16985) Fix data missing issue when delete local block file.

[ https://issues.apache.org/jira/browse/HDFS-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16985: --- Summary: Fix data missing issue when delete local block file. (was: delete local block file when Fil

[jira] [Resolved] (HDFS-16985) Fix data missing issue when delete local block file.

[ https://issues.apache.org/jira/browse/HDFS-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16985. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Target Version/s: (was: 3.3.1)

[jira] [Updated] (HDFS-16909) Improve ReplicaMap#mergeAll method.

[ https://issues.apache.org/jira/browse/HDFS-16909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16909: --- Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Affects Version/s: (was: 3.3.4)

[jira] [Updated] (HDFS-17026) RBF: NamenodeHeartbeatService should update JMX report with configurable frequency

[ https://issues.apache.org/jira/browse/HDFS-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17026: --- Summary: RBF: NamenodeHeartbeatService should update JMX report with configurable frequency (was: Na

[jira] [Commented] (HDFS-17026) RBF: NamenodeHeartbeatService should update JMX report with configurable frequency

[ https://issues.apache.org/jira/browse/HDFS-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726451#comment-17726451 ] Xiaoqiao He commented on HDFS-17026: {quote}We should configure the NamenodeHeartbeat

[jira] [Resolved] (HDFS-17026) RBF: NamenodeHeartbeatService should update JMX report with configurable frequency

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

[jira] [Commented] (HDFS-17026) RBF: NamenodeHeartbeatService should update JMX report with configurable frequency

[ https://issues.apache.org/jira/browse/HDFS-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728183#comment-17728183 ] Xiaoqiao He commented on HDFS-17026: [~hchaverri] Please submit this PR for branch-3.

[jira] [Updated] (HDFS-17003) Erasure Coding: invalidate wrong block after reporting bad blocks from datanode

[ https://issues.apache.org/jira/browse/HDFS-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17003: --- Summary: Erasure Coding: invalidate wrong block after reporting bad blocks from datanode (was: Erasu

[jira] [Resolved] (HDFS-17003) Erasure Coding: invalidate wrong block after reporting bad blocks from datanode

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

[jira] [Updated] (HDFS-17003) Erasure Coding: invalidate wrong block after reporting bad blocks from datanode

[ https://issues.apache.org/jira/browse/HDFS-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17003: --- Component/s: namenode > Erasure Coding: invalidate wrong block after reporting bad blocks from > dat

[jira] [Commented] (HDFS-17003) Erasure Coding: invalidate wrong block after reporting bad blocks from datanode

[ https://issues.apache.org/jira/browse/HDFS-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730500#comment-17730500 ] Xiaoqiao He commented on HDFS-17003: cherry-pick to branch-3.3. > Erasure Coding: i

[jira] [Updated] (HDFS-17003) Erasure Coding: invalidate wrong block after reporting bad blocks from datanode

[ https://issues.apache.org/jira/browse/HDFS-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17003: --- Fix Version/s: 3.3.6 > Erasure Coding: invalidate wrong block after reporting bad blocks from > data

[jira] [Resolved] (HDFS-17037) Consider nonDfsUsed when running balancer

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

[jira] [Updated] (HDFS-17037) Consider nonDfsUsed when running balancer

[ https://issues.apache.org/jira/browse/HDFS-17037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17037: --- Component/s: balamcer Issue Type: Improvement (was: Bug) > Consider nonDfsUsed when running bal

[jira] [Updated] (HDFS-17037) Consider nonDfsUsed when running balancer

[ https://issues.apache.org/jira/browse/HDFS-17037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17037: --- Component/s: balancer & mover (was: balamcer) > Consider nonDfsUsed when running

[jira] [Commented] (HDFS-16898) Remove write lock for processCommandFromActor of DataNode to reduce impact on heartbeat

[ https://issues.apache.org/jira/browse/HDFS-16898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731448#comment-17731448 ] Xiaoqiao He commented on HDFS-16898: Committed to branch-3.3. > Remove write lock fo

[jira] [Updated] (HDFS-16898) Remove write lock for processCommandFromActor of DataNode to reduce impact on heartbeat

[ https://issues.apache.org/jira/browse/HDFS-16898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16898: --- Fix Version/s: 3.3.7 > Remove write lock for processCommandFromActor of DataNode to reduce impact on

[jira] [Commented] (HDFS-17046) Add metrics or delete directly when path can not parsed in Trash.

[ https://issues.apache.org/jira/browse/HDFS-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732023#comment-17732023 ] Xiaoqiao He commented on HDFS-17046: Thanks [~zhanghaobo] for your report. Do you mea

[jira] [Commented] (HDFS-17048) FSNamesystem.delete() maybe cause data residue when active namenode crash or shutdown

[ https://issues.apache.org/jira/browse/HDFS-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732434#comment-17732434 ] Xiaoqiao He commented on HDFS-17048: [~liuguanghua] Thanks for your report. Sorry I d

[jira] [Resolved] (HDFS-17049) EC: Fix duplicate block group IDs generated by SequentialBlockGroupIdGenerator

[ https://issues.apache.org/jira/browse/HDFS-17049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-17049. Resolution: Not A Problem > EC: Fix duplicate block group IDs generated by SequentialBlockGroupIdGe

[jira] [Commented] (HDFS-6994) libhdfs3 - A native C/C++ HDFS client

[ https://issues.apache.org/jira/browse/HDFS-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735663#comment-17735663 ] Xiaoqiao He commented on HDFS-6994: --- Hi [~wangzw],[~cmccabe], Thanks for your great work

[jira] [Updated] (HDFS-17044) Set size of non-exist block to NO_ACK when process FBR or IBR to avoid useless report from DataNode

[ https://issues.apache.org/jira/browse/HDFS-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17044: --- Summary: Set size of non-exist block to NO_ACK when process FBR or IBR to avoid useless report from D

[jira] [Resolved] (HDFS-17044) Set size of non-exist block to NO_ACK when process FBR or IBR to avoid useless report from DataNode

[ https://issues.apache.org/jira/browse/HDFS-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-17044. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed > Set size of non-exist b

[jira] [Updated] (HDFS-17044) Set size of non-exist block to NO_ACK when process FBR or IBR to avoid useless report from DataNode

[ https://issues.apache.org/jira/browse/HDFS-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17044: --- Component/s: namenode > Set size of non-exist block to NO_ACK when process FBR or IBR to avoid > use

[jira] [Resolved] (HDFS-17052) Improve BlockPlacementPolicyRackFaultTolerant to avoid choose nodes failed when no enough Rack.

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

[jira] [Commented] (HDFS-17071) Erasure coding: delete duplicated ec block with same block group id on one datanode.

[ https://issues.apache.org/jira/browse/HDFS-17071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740925#comment-17740925 ] Xiaoqiao He commented on HDFS-17071: I found that this JIRA report the same issue as

[jira] [Commented] (HDFS-17072) DFSAdmin: add a triggerVolumeScanner command

[ https://issues.apache.org/jira/browse/HDFS-17072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740926#comment-17740926 ] Xiaoqiao He commented on HDFS-17072: Thanks to involve me here. +1 from my side. > D

[jira] [Resolved] (HDFS-17073) Enhance the warning message output for BlockGroupNonStripedChecksumComputer#compute

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

[jira] [Resolved] (HDFS-17033) Update fsck to display stale state info of blocks accurately

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

[jira] [Created] (HDFS-17090) Decommission will be stuck for long time when restart because overlapped process Register and BlockReport.

Xiaoqiao He created HDFS-17090: -- Summary: Decommission will be stuck for long time when restart because overlapped process Register and BlockReport. Key: HDFS-17090 URL: https://issues.apache.org/jira/browse/HDFS-170

[jira] [Commented] (HDFS-17090) Decommission will be stuck for long time when restart because overlapped process Register and BlockReport.

[ https://issues.apache.org/jira/browse/HDFS-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743790#comment-17743790 ] Xiaoqiao He commented on HDFS-17090: We mark `DatanodeProtocol#registerDatanode` inte

[jira] [Commented] (HDFS-17093) In the case of all datanodes sending FBR when the namenode restarts (large clusters), there is an issue with incomplete block reporting

[ https://issues.apache.org/jira/browse/HDFS-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744424#comment-17744424 ] Xiaoqiao He commented on HDFS-17093: [~yuyanlei] Thanks for your report, Would you tr

[jira] [Commented] (HDFS-17097) Out of Memory when set dfs.namenode.blockreport.queue.size to a large number

[ https://issues.apache.org/jira/browse/HDFS-17097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744429#comment-17744429 ] Xiaoqiao He commented on HDFS-17097: [~FuzzingTeam] Thanks for your report. We receiv

[jira] [Comment Edited] (HDFS-17097) Out of Memory when set dfs.namenode.blockreport.queue.size to a large number

[ https://issues.apache.org/jira/browse/HDFS-17097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744429#comment-17744429 ] Xiaoqiao He edited comment on HDFS-17097 at 7/19/23 3:54 AM: -

[jira] [Commented] (HDFS-17093) In the case of all datanodes sending FBR when the namenode restarts (large clusters), there is an issue with incomplete block reporting

[ https://issues.apache.org/jira/browse/HDFS-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744526#comment-17744526 ] Xiaoqiao He commented on HDFS-17093: {quote}# DN wants to send 12 reports but only se

[jira] [Commented] (HDFS-17097) Out of Memory when set dfs.namenode.blockreport.queue.size to a large number

[ https://issues.apache.org/jira/browse/HDFS-17097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746189#comment-17746189 ] Xiaoqiao He commented on HDFS-17097: [~FuzzingTeam] Great, I try to search JIRA from

[jira] [Resolved] (HDFS-17112) Show decommission duration in JMX and HTML

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

[jira] [Updated] (HDFS-17112) Show decommission duration in JMX and HTML

[ https://issues.apache.org/jira/browse/HDFS-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17112: --- Component/s: namenode > Show decommission duration in JMX and HTML >

[jira] [Updated] (HDFS-17090) Decommission will be stuck for long time when restart because overlapped process Register and BlockReport.

[ https://issues.apache.org/jira/browse/HDFS-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17090: --- Description: I met one corner case recently, which decommission DataNode impact performance of NameN

[jira] [Updated] (HDFS-17117) Print reconstructionQueuesInitProgress periodically when BlockManager processMisReplicatesAsync.

[ https://issues.apache.org/jira/browse/HDFS-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17117: --- Summary: Print reconstructionQueuesInitProgress periodically when BlockManager processMisReplicatesAs

[jira] [Updated] (HDFS-17117) Print reconstructionQueuesInitProgress periodically when BlockManager processMisReplicatesAsync.

[ https://issues.apache.org/jira/browse/HDFS-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17117: --- Component/s: namenode > Print reconstructionQueuesInitProgress periodically when BlockManager > proc

[jira] [Resolved] (HDFS-17117) Print reconstructionQueuesInitProgress periodically when BlockManager processMisReplicatesAsync.

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

[jira] [Resolved] (HDFS-17116) RBF: Update invoke millisecond time as monotonicNow() in RouterSafemodeService.

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

[jira] [Updated] (HDFS-17116) RBF: Update invoke millisecond time as monotonicNow() in RouterSafemodeService.

[ https://issues.apache.org/jira/browse/HDFS-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17116: --- Summary: RBF: Update invoke millisecond time as monotonicNow() in RouterSafemodeService. (was: Reset

[jira] [Resolved] (HDFS-17134) RBF: Fix duplicate results of getListing through Router.

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

[jira] [Updated] (HDFS-17134) RBF: Fix duplicate results of getListing through Router.

[ https://issues.apache.org/jira/browse/HDFS-17134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17134: --- Component/s: rbf > RBF: Fix duplicate results of getListing through Router. > ---

[jira] [Commented] (HDFS-17138) RBF: We changed the hadoop.security.auth_to_local configuration of one router, the other routers stopped working

[ https://issues.apache.org/jira/browse/HDFS-17138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750537#comment-17750537 ] Xiaoqiao He commented on HDFS-17138: Thanks. IMO, it may be one common issue, not aff

[jira] [Assigned] (HDFS-17140) Optimize the BPOfferService.reportBadBlocks() method

[ https://issues.apache.org/jira/browse/HDFS-17140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-17140: -- Assignee: Liangjun He > Optimize the BPOfferService.reportBadBlocks() method > ---

[jira] [Assigned] (HDFS-17141) Optimize the default parameters for the FileUtil.isRegularFile() method

[ https://issues.apache.org/jira/browse/HDFS-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-17141: -- Assignee: Liangjun He > Optimize the default parameters for the FileUtil.isRegularFile() metho

[jira] [Commented] (HDFS-17138) RBF: We changed the hadoop.security.auth_to_local configuration of one router, the other routers stopped working

[ https://issues.apache.org/jira/browse/HDFS-17138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751456#comment-17751456 ] Xiaoqiao He commented on HDFS-17138: {quote}Other modules are also using subclasses o

[jira] [Updated] (HDFS-17137) Standby/Observer NameNode skip to handle redundant replica block logic when set decrease replication.

[ https://issues.apache.org/jira/browse/HDFS-17137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17137: --- Summary: Standby/Observer NameNode skip to handle redundant replica block logic when set decrease rep

[jira] [Resolved] (HDFS-17137) Standby/Observer NameNode skip to handle redundant replica block logic when set decrease replication.

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

[jira] [Updated] (HDFS-17137) Standby/Observer NameNode skip to handle redundant replica block logic when set decrease replication.

[ https://issues.apache.org/jira/browse/HDFS-17137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17137: --- Component/s: namenode > Standby/Observer NameNode skip to handle redundant replica block logic when

[jira] [Commented] (HDFS-17149) getBlockLocations RPC should use actual client ip to compute network distance when using RBF.

[ https://issues.apache.org/jira/browse/HDFS-17149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752284#comment-17752284 ] Xiaoqiao He commented on HDFS-17149: Hi [~zhanghaobo], Please check if HDFS-15079 can

[jira] [Commented] (HDFS-17149) getBlockLocations RPC should use actual client ip to compute network distance when using RBF.

[ https://issues.apache.org/jira/browse/HDFS-17149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753895#comment-17753895 ] Xiaoqiao He commented on HDFS-17149: [~zhanghaobo], Thanks, IIRC, there are many and

[jira] [Resolved] (HDFS-17150) EC: Fix the bug of failed lease recovery.

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

[jira] [Assigned] (HDFS-17150) EC: Fix the bug of failed lease recovery.

[ https://issues.apache.org/jira/browse/HDFS-17150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-17150: -- Assignee: Shuyan Zhang > EC: Fix the bug of failed lease recovery. > -

[jira] [Resolved] (HDFS-17154) EC: Fix bug in updateBlockForPipeline after failover

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

[jira] [Assigned] (HDFS-17151) EC: Fix wrong metadata in BlockInfoStriped after recovery

[ https://issues.apache.org/jira/browse/HDFS-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-17151: -- Assignee: Shuyan Zhang > EC: Fix wrong metadata in BlockInfoStriped after recovery > -

[jira] [Resolved] (HDFS-17151) EC: Fix wrong metadata in BlockInfoStriped after recovery

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

[jira] [Updated] (HDFS-17093) Fix block report lease issue to avoid missing some storages report.

[ https://issues.apache.org/jira/browse/HDFS-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17093: --- Summary: Fix block report lease issue to avoid missing some storages report. (was: In the case of al

[jira] [Assigned] (HDFS-17093) Fix block report lease issue to avoid missing some storages report.

[ https://issues.apache.org/jira/browse/HDFS-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-17093: -- Assignee: Yanlei Yu > Fix block report lease issue to avoid missing some storages report. > --

[jira] [Resolved] (HDFS-17093) Fix block report lease issue to avoid missing some storages report.

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

[jira] [Commented] (HDFS-17175) setOwner maybe set any user due to HDFS-16798

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

[jira] [Commented] (HDFS-17175) setOwner maybe set any user due to HDFS-16798

[ https://issues.apache.org/jira/browse/HDFS-17175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761615#comment-17761615 ] Xiaoqiao He commented on HDFS-17175: Great, let's try to push this bugfix to checkin.

[jira] [Updated] (HDFS-16933) A race in SerialNumberMap will cause wrong owner, group and XATTR

[ https://issues.apache.org/jira/browse/HDFS-16933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16933: --- Summary: A race in SerialNumberMap will cause wrong owner, group and XATTR (was: A race in SerialNum

[jira] [Resolved] (HDFS-16933) A race in SerialNumberMap will cause wrong owner, group and XATTR

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

[jira] [Resolved] (HDFS-17140) Revisit the BPOfferService.reportBadBlocks() method.

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

[jira] [Updated] (HDFS-17140) Revisit the BPOfferService.reportBadBlocks() method.

[ https://issues.apache.org/jira/browse/HDFS-17140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17140: --- Summary: Revisit the BPOfferService.reportBadBlocks() method. (was: Optimize the BPOfferService.repo

[jira] [Resolved] (HDFS-17190) EC: Fix bug of OIV processing XAttr.

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

[jira] [Resolved] (HDFS-17192) Add bock info when constructing remote block reader meets IOException

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

[jira] [Resolved] (HDFS-17105) mistakenly purge editLogs even after it is empty in NNStorageRetentionManager

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

[jira] [Updated] (HDFS-17105) mistakenly purge editLogs even after it is empty in NNStorageRetentionManager

[ https://issues.apache.org/jira/browse/HDFS-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17105: --- Priority: Minor (was: Critical) > mistakenly purge editLogs even after it is empty in NNStorageRete

[jira] [Resolved] (HDFS-17184) Improve BlockReceiver to throws DiskOutOfSpaceException when initialize

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

[jira] [Updated] (HDFS-17184) Improve BlockReceiver to throws DiskOutOfSpaceException when initialize

[ https://issues.apache.org/jira/browse/HDFS-17184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17184: --- Summary: Improve BlockReceiver to throws DiskOutOfSpaceException when initialize (was: In BlockRecei

[jira] [Assigned] (HDFS-17197) Show file replication when listing corrupt files.

[ https://issues.apache.org/jira/browse/HDFS-17197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-17197: -- Assignee: Shuyan Zhang > Show file replication when listing corrupt files. > -

[jira] [Resolved] (HDFS-17197) Show file replication when listing corrupt files.

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

[jira] [Updated] (HDFS-17204) EC: Reduce unnecessary log when processing excess redundancy.

[ https://issues.apache.org/jira/browse/HDFS-17204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17204: --- Component/s: ec > EC: Reduce unnecessary log when processing excess redundancy. > ---

[jira] [Resolved] (HDFS-17204) EC: Reduce unnecessary log when processing excess redundancy.

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

[jira] [Commented] (HDFS-17218) NameNode should remove its excess blocks from the ExcessRedundancyMap When a DN registers

[ https://issues.apache.org/jira/browse/HDFS-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773095#comment-17773095 ] Xiaoqiao He commented on HDFS-17218: Thanks for your report. {quote}it causes some bl

[jira] [Commented] (HDFS-17218) NameNode should remove its excess blocks from the ExcessRedundancyMap When a DN registers

[ https://issues.apache.org/jira/browse/HDFS-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773523#comment-17773523 ] Xiaoqiao He commented on HDFS-17218: {quote}6. dn restarts will FBR is executed (proc

[jira] [Resolved] (HDFS-17208) Add the metrics PendingAsyncDiskOperations in datanode

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

[jira] [Resolved] (HDFS-17217) Add lifeline RPC start up log when NameNode#startCommonServices

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

[jira] [Assigned] (HDFS-17231) HA: Safemode should exit when resources are from low to available

[ https://issues.apache.org/jira/browse/HDFS-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-17231: -- Assignee: kuper > HA: Safemode should exit when resources are from low to available >

[jira] [Commented] (HDFS-17231) HA: Safemode should exit when resources are from low to available

[ https://issues.apache.org/jira/browse/HDFS-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778520#comment-17778520 ] Xiaoqiao He commented on HDFS-17231: Add [~kuper] to contributor list and assign this

[jira] [Resolved] (HDFS-17231) HA: Safemode should exit when resources are from low to available

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

[jira] [Commented] (HDFS-17241) long write lock on active NN from rollEditLog()

[ https://issues.apache.org/jira/browse/HDFS-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780797#comment-17780797 ] Xiaoqiao He commented on HDFS-17241: Hi [~shuaiqi.guo], Thanks for your report and co

[jira] [Commented] (HDFS-16016) BPServiceActor add a new thread to handle IBR

[ https://issues.apache.org/jira/browse/HDFS-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783162#comment-17783162 ] Xiaoqiao He commented on HDFS-16016: [~yuanbo] Thanks involve me here again. IIRC, we

[jira] [Updated] (HDFS-17063) Support to configure different capacity reserved for each disk of DataNode.

[ https://issues.apache.org/jira/browse/HDFS-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-17063: --- Summary: Support to configure different capacity reserved for each disk of DataNode. (was: Datanode

[jira] [Resolved] (HDFS-17172) Support FSNamesystemLock Parameters reconfigurable

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

[jira] [Resolved] (HDFS-17063) Support to configure different capacity reserved for each disk of DataNode.

[ https://issues.apache.org/jira/browse/HDFS-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-17063. Fix Version/s: 3.4.0 Resolution: Fixed > Support to configure different capacity reserved fo

<    5   6   7   8   9   10   11   >