[jira] [Updated] (HDFS-15273) CacheReplicationMonitor hold lock for long time and lead to NN out of service

[ https://issues.apache.org/jira/browse/HDFS-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15273: --- Attachment: HDFS-15273.002.patch > CacheReplicationMonitor hold lock for long time and lead to NN

[jira] [Commented] (HDFS-15273) CacheReplicationMonitor hold lock for long time and lead to NN out of service

[ https://issues.apache.org/jira/browse/HDFS-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505270#comment-17505270 ] Xiaoqiao He commented on HDFS-15273: Thanks [~weichiu] for your reminder. update the patch with

[jira] [Updated] (HDFS-16428) Source path with storagePolicy cause wrong typeConsumed while rename

[ https://issues.apache.org/jira/browse/HDFS-16428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16428: --- Fix Version/s: 3.2.3 3.3.3 Thanks [~prasad-acit] for your reminder, cherry-pick

[jira] [Commented] (HDFS-15382) Split FsDatasetImpl from blockpool lock to blockpool volume lock

[ https://issues.apache.org/jira/browse/HDFS-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495328#comment-17495328 ] Xiaoqiao He commented on HDFS-15382: Thanks [~yuanbo] for your feedback. [~Aiphag0] is working for

[jira] [Commented] (HDFS-15987) Improve oiv tool to parse fsimage file in parallel with delimited format

[ https://issues.apache.org/jira/browse/HDFS-15987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510993#comment-17510993 ] Xiaoqiao He commented on HDFS-15987: revert and re-check in to correct the git message. > Improve

[jira] [Resolved] (HDFS-16504) Add parameter for NameNode to process getBloks request

[ https://issues.apache.org/jira/browse/HDFS-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16504. Resolution: Fixed > Add parameter for NameNode to process getBloks request >

[jira] [Updated] (HDFS-16504) Add parameter for NameNode to process getBloks request

[ https://issues.apache.org/jira/browse/HDFS-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16504: --- Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Summary: Add parameter for NameNode to

[jira] [Commented] (HDFS-15273) CacheReplicationMonitor hold lock for long time and lead to NN out of service

[ https://issues.apache.org/jira/browse/HDFS-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511029#comment-17511029 ] Xiaoqiao He commented on HDFS-15273: Submit v003 patch and trigger Yetus again. [~weichiu] Would you

[jira] [Updated] (HDFS-15273) CacheReplicationMonitor hold lock for long time and lead to NN out of service

[ https://issues.apache.org/jira/browse/HDFS-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15273: --- Attachment: HDFS-15273.003.patch > CacheReplicationMonitor hold lock for long time and lead to NN

[jira] [Resolved] (HDFS-16498) Fix NPE for checkBlockReportLease

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

[jira] [Updated] (HDFS-16511) Improve lock type for ReplicaMap under fine-grain lock mode.

[ https://issues.apache.org/jira/browse/HDFS-16511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16511: --- Summary: Improve lock type for ReplicaMap under fine-grain lock mode. (was: Change some frequent

[jira] [Updated] (HDFS-16511) Improve lock type for ReplicaMap under fine-grain lock mode.

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

[jira] [Resolved] (HDFS-15987) Improve oiv tool to parse fsimage file in parallel with delimited format

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

[jira] [Resolved] (HDFS-16429) Add DataSetLockManager to manage fine-grain locks for FsDataSetImpl

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

[jira] [Updated] (HDFS-16429) Add DataSetLockManager to manage fine-grain locks for FsDataSetImpl

[ https://issues.apache.org/jira/browse/HDFS-16429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16429: --- Summary: Add DataSetLockManager to manage fine-grain locks for FsDataSetImpl (was: Add

[jira] [Updated] (HDFS-16402) Improve HeartbeatManager logic to avoid incorrect stats

[ https://issues.apache.org/jira/browse/HDFS-16402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16402: --- Summary: Improve HeartbeatManager logic to avoid incorrect stats (was: HeartbeatManager may cause

[jira] [Resolved] (HDFS-16402) Improve HeartbeatManager logic to avoid incorrect stats

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

[jira] [Updated] (HDFS-16428) Source path with storagePolicy cause wrong typeConsumed while rename

[ https://issues.apache.org/jira/browse/HDFS-16428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16428: --- Summary: Source path with storagePolicy cause wrong typeConsumed while rename (was: Source path

[jira] [Resolved] (HDFS-16428) Source path with storagePolicy cause wrong typeConsumed while rename

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

[jira] [Updated] (HDFS-16429) Add DataSetLockManager to maintain locks for FsDataSetImpl

[ https://issues.apache.org/jira/browse/HDFS-16429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16429: --- Fix Version/s: (was: 3.2.0) Target Version/s: (was: 3.2.0) Affects Version/s:

[jira] [Assigned] (HDFS-16516) fix filesystemshell wrong params

[ https://issues.apache.org/jira/browse/HDFS-16516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reassigned HDFS-16516: -- Assignee: guophilipse > fix filesystemshell wrong params > >

[jira] [Resolved] (HDFS-16516) fix filesystemshell wrong params

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

[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=17761615#comment-17761615 ] Xiaoqiao He commented on HDFS-17175: Great, let's try to push this bugfix to checkin. > setOwner

[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

[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

[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

[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

[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=17761148#comment-17761148 ] Xiaoqiao He commented on HDFS-17175: Thanks [~Linwood] for your report. It is true for the first

[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=17780797#comment-17780797 ] Xiaoqiao He commented on HDFS-17241: Hi [~shuaiqi.guo], Thanks for your report and contribution.

[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

[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=17783162#comment-17783162 ] Xiaoqiao He commented on HDFS-16016: [~yuanbo] Thanks involve me here again. IIRC, we mentioned times

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

[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

[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

[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

[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

[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=17773095#comment-17773095 ] Xiaoqiao He commented on HDFS-17218: Thanks for your report. {quote}it causes some blocks in the

[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

[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

[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=17778520#comment-17778520 ] Xiaoqiao He commented on HDFS-17231: Add [~kuper] to contributor list and assign this JIRA to

[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-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=17773523#comment-17773523 ] Xiaoqiao He commented on HDFS-17218: {quote}6. dn restarts will FBR is executed

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

[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

[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] [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] [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=17753895#comment-17753895 ] Xiaoqiao He commented on HDFS-17149: [~zhanghaobo], Thanks, IIRC, there are many and many times we

[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

[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] [Commented] (HDFS-16531) Avoid setReplication logging an edit record if old replication equals the new value

[ https://issues.apache.org/jira/browse/HDFS-16531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17525408#comment-17525408 ] Xiaoqiao He commented on HDFS-16531: Thanks [~ayushtkn] for your kind information. Based on above

[jira] [Resolved] (HDFS-16500) Make asynchronous blocks deletion lock and unlock durtion threshold configurable

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

[jira] [Commented] (HDFS-16531) Avoid setReplication logging an edit record if old replication equals the new value

[ https://issues.apache.org/jira/browse/HDFS-16531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17525415#comment-17525415 ] Xiaoqiao He commented on HDFS-16531: [~hemanthboyina], Thanks very much for your reminder and the

[jira] [Resolved] (HDFS-16554) Remove unused configuration dfs.namenode.block.deletion.increment.

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

[jira] [Updated] (HDFS-16554) Remove unused configuration dfs.namenode.block.deletion.increment.

[ https://issues.apache.org/jira/browse/HDFS-16554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16554: --- Component/s: namenode > Remove unused configuration dfs.namenode.block.deletion.increment. >

[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=17561997#comment-17561997 ] Xiaoqiao He commented on HDFS-15079: [~xuzq_zander] Thanks to involve me here. I am not fans about

[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

[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

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

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

[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] [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=17555638#comment-17555638 ] Xiaoqiao He commented on HDFS-16600: [~xuzq_zander] BTW, do you deploy this feature on your prod

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

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

[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

[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

[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

[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

[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=17553086#comment-17553086 ] Xiaoqiao He commented on HDFS-16627: [~slfan1989] BTW, the fix version label should be not set when

[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

[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

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

[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=17566132#comment-17566132 ] Xiaoqiao He commented on HDFS-16657: [~yuanbo] Thanks for your proposal. IIRC, we has discussed this

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

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

[jira] [Resolved] (HDFS-16534) Split datanode block pool locks to volume grain.

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

[jira] [Updated] (HDFS-15382) Split one FsDatasetImpl lock to volume grain locks.

[ https://issues.apache.org/jira/browse/HDFS-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15382: --- Release Note: Throughput is one of the core performance evaluation for DataNode instance. However it

[jira] [Commented] (HDFS-15382) Split one FsDatasetImpl lock to volume grain locks.

[ https://issues.apache.org/jira/browse/HDFS-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1752#comment-1752 ] Xiaoqiao He commented on HDFS-15382: This big improvement has been ready completely now. Thanks

[jira] [Resolved] (HDFS-16531) Avoid setReplication logging an edit record if old replication equals the new value

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

[jira] [Resolved] (HDFS-16509) Fix decommission UnsupportedOperationException: Remove unsupported

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

[jira] [Commented] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532747#comment-17532747 ] Xiaoqiao He commented on HDFS-16569: [~yuanbo] Thanks for your report. Do you mean that last block

[jira] [Commented] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532755#comment-17532755 ] Xiaoqiao He commented on HDFS-16565: [~jianghuazhu] Thanks for your report. Is it possible that

[jira] [Commented] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532790#comment-17532790 ] Xiaoqiao He commented on HDFS-16569: Thanks [~yuanbo] for your detailed explanation. It is an

[jira] [Comment Edited] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532790#comment-17532790 ] Xiaoqiao He edited comment on HDFS-16569 at 5/6/22 11:22 AM: - Thanks

[jira] [Updated] (HDFS-16553) Fix checkstyle for the length of BlockManager construction method over limit.

[ https://issues.apache.org/jira/browse/HDFS-16553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-16553: --- Component/s: namenode > Fix checkstyle for the length of BlockManager construction method over

[jira] [Resolved] (HDFS-16553) Fix checkstyle for the length of BlockManager construction method over limit.

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

[jira] [Commented] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534276#comment-17534276 ] Xiaoqiao He commented on HDFS-16569: {quote}Regarding Tectonic, seperating deamon threads from NN and

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

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

[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=17624847#comment-17624847 ] Xiaoqiao He commented on HDFS-10453: [~yuyanlei] It works find in my internal cluster. It has been

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

<    4   5   6   7   8   9   10   11   >