[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=17221107#comment-17221107 ] Xiaoqiao He commented on HDFS-15651: {quote}The blocktoken key will be updated for every

[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: --- Assignee: Aiphago Status: Patch Available (was: Open) Try to trigger Yetus manually. >

[jira] [Commented] (HDFS-15641) DataNode could meet deadlock if invoke refreshNameNode

[ https://issues.apache.org/jira/browse/HDFS-15641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17220744#comment-17220744 ] Xiaoqiao He commented on HDFS-15641: Thanks [~wanghongbing],[~ferhui] for your works here, and sorry

[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=17220749#comment-17220749 ] Xiaoqiao He commented on HDFS-15651: Thanks [~linyiqun] for your report. Catch the error and loop

[jira] [Commented] (HDFS-15644) Failed volumes can cause DNs to stop block reporting

[ https://issues.apache.org/jira/browse/HDFS-15644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17220765#comment-17220765 ] Xiaoqiao He commented on HDFS-15644: Hi [~weichiu],[~ahussein], Just found that fix versions include

[jira] [Commented] (HDFS-15448) When starting a DataNode, call BlockPoolManager#startAll() twice.

[ https://issues.apache.org/jira/browse/HDFS-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148723#comment-17148723 ] Xiaoqiao He commented on HDFS-15448: Thanks [~jianghuazhu], Good catch here. v001 almost LGTM, just

[jira] [Commented] (HDFS-15416) Improve DataStorage#addStorageLocations() for empty locations

[ https://issues.apache.org/jira/browse/HDFS-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148729#comment-17148729 ] Xiaoqiao He commented on HDFS-15416: LGTM, +1 on v001. Thanks [~jianghuazhu] for your catches here.

[jira] [Commented] (HDFS-15416) Improve DataStorage#addStorageLocations() for empty locations

[ https://issues.apache.org/jira/browse/HDFS-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148731#comment-17148731 ] Xiaoqiao He commented on HDFS-15416: BTW, it is better to trace or review for participants if we keep

[jira] [Comment Edited] (HDFS-15448) When starting a DataNode, call BlockPoolManager#startAll() twice.

[ https://issues.apache.org/jira/browse/HDFS-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148723#comment-17148723 ] Xiaoqiao He edited comment on HDFS-15448 at 6/30/20, 2:24 PM: -- Thanks

[jira] [Commented] (HDFS-15452) Dynamically initialize the capacity of BlocksMap

[ https://issues.apache.org/jira/browse/HDFS-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154314#comment-17154314 ] Xiaoqiao He commented on HDFS-15452: Thanks involve me here. Sorry I don't get what issues do you

[jira] [Commented] (HDFS-15448) When starting a DataNode, call BlockPoolManager#startAll() twice.

[ https://issues.apache.org/jira/browse/HDFS-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153311#comment-17153311 ] Xiaoqiao He commented on HDFS-15448: LGTM, +1 for [^HDFS-15448.003.patch]. > When starting a

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153702#comment-17153702 ] Xiaoqiao He commented on HDFS-14498: Thanks [~sodonnell]. [^HDFS-14498.001.patch] LGTM almost. just

[jira] [Updated] (HDFS-15425) Review Logging of DFSClient

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

[jira] [Updated] (HDFS-15425) Review Logging of DFSClient

[ https://issues.apache.org/jira/browse/HDFS-15425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15425: --- Component/s: dfsclient > Review Logging of DFSClient > --- > >

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152228#comment-17152228 ] Xiaoqiao He commented on HDFS-14498: Thanks [~sodonnell] for your quick response. {quote}the

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152196#comment-17152196 ] Xiaoqiao He commented on HDFS-14498: [~sodonnell] thanks for your deep dig of this issue. I try to

[jira] [Commented] (HDFS-15425) Review Logging of DFSClient

[ https://issues.apache.org/jira/browse/HDFS-15425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152149#comment-17152149 ] Xiaoqiao He commented on HDFS-15425: LGTM. +1 on [^HDFS-15425.003.patch]. will commit shortly. >

[jira] [Resolved] (HDFS-15451) Restarting name node stuck in safe mode when using provided storage

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

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

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

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156513#comment-17156513 ] Xiaoqiao He commented on HDFS-14498: cherry-pick to branches 3.3/3.2/3.1/2.10. > LeaseManager can

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14498: --- Fix Version/s: 3.1.5 3.3.1 2.10.1 3.2.2 >

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14498: --- Fix Version/s: (was: 2.10.1) > LeaseManager can loop forever on the file for which create has

[jira] [Reopened] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reopened HDFS-14498: > LeaseManager can loop forever on the file for which create has failed >

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

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

[jira] [Comment Edited] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156816#comment-17156816 ] Xiaoqiao He edited comment on HDFS-14498 at 7/13/20, 4:11 PM: -- Thanks

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14498: --- Attachment: HDFS-14498-branch-3.2.001.patch HDFS-14498-branch-3.1.001.patch

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157155#comment-17157155 ] Xiaoqiao He commented on HDFS-14498: Thanks [~epayne],[~ebadger] for your operation suggestions. I

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14498: --- Attachment: HDFS-14498-branch-2.10.002.patch > LeaseManager can loop forever on the file for which

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14498: --- Attachment: HDFS-14498-branch-3.1.001.patch > LeaseManager can loop forever on the file for which

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157486#comment-17157486 ] Xiaoqiao He commented on HDFS-14498: submit [^HDFS-14498-branch-3.1.001.patch] and

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157870#comment-17157870 ] Xiaoqiao He commented on HDFS-14498: re-submit [^HDFS-14498-branch-3.1.001.patch] without any changes

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14498: --- Attachment: HDFS-14498-branch-3.1.001.patch > LeaseManager can loop forever on the file for which

[jira] [Commented] (HDFS-15469) Dynamically configure the size of PacketReceiver#MAX_PACKET_SIZE

[ https://issues.apache.org/jira/browse/HDFS-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157880#comment-17157880 ] Xiaoqiao He commented on HDFS-15469: Thanks [~jianghuazhu] involve me here. Sorry I do not have

[jira] [Comment Edited] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158144#comment-17158144 ] Xiaoqiao He edited comment on HDFS-14498 at 7/15/20, 1:10 PM: -- Check failed

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158144#comment-17158144 ] Xiaoqiao He commented on HDFS-14498: Check failed unit tests for branch-2.10/branch-3.1 and run

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157305#comment-17157305 ] Xiaoqiao He commented on HDFS-14498: Hi [~sodonnell], patch for branch-3.1/3.2 only remove the final

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156474#comment-17156474 ] Xiaoqiao He commented on HDFS-14498: Thanks [~sodonnell] for your double checks. Will commit it later

[jira] [Updated] (HDFS-15416) Improve DataStorage#addStorageLocations() for empty locations

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

[jira] [Updated] (HDFS-15416) Improve DataStorage#addStorageLocations() for empty locations

[ https://issues.apache.org/jira/browse/HDFS-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15416: --- Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available)

[jira] [Commented] (HDFS-15448) When starting a DataNode, call BlockPoolManager#startAll() twice.

[ https://issues.apache.org/jira/browse/HDFS-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149152#comment-17149152 ] Xiaoqiao He commented on HDFS-15448: Ping [~weichiu],[~elgoiri],[~linyiqun], would you like to have

[jira] [Commented] (HDFS-15448) When starting a DataNode, call BlockPoolManager#startAll() twice.

[ https://issues.apache.org/jira/browse/HDFS-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149897#comment-17149897 ] Xiaoqiao He commented on HDFS-15448: Hi [~linyiqun], As [~jianghuazhu] mentioned above,

[jira] [Commented] (HDFS-15448) When starting a DataNode, call BlockPoolManager#startAll() twice.

[ https://issues.apache.org/jira/browse/HDFS-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149091#comment-17149091 ] Xiaoqiao He commented on HDFS-15448: {quote}whether your suggestion is to increase synchronization

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154161#comment-17154161 ] Xiaoqiao He commented on HDFS-14498: [^HDFS-14498.002.patch] LGTM, +1 from my side. > LeaseManager

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155075#comment-17155075 ] Xiaoqiao He commented on HDFS-14498: Hi [~weichiu] and every watchers, Any other review comments

[jira] [Commented] (HDFS-15105) Standby NN exits and fails to restart due to edit log corruption

[ https://issues.apache.org/jira/browse/HDFS-15105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146036#comment-17146036 ] Xiaoqiao He commented on HDFS-15105: [~Tao Yang] Do you enable async editlog feature, Not sure if is

[jira] [Assigned] (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 reassigned HDFS-15175: -- Assignee: Wan Chang (was: Yicong Cai) > Multiple CloseOp shared block instance causes the

[jira] [Commented] (HDFS-15391) Standby NameNode due loads the corruption edit log, the service exits and cannot be restarted

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135683#comment-17135683 ] Xiaoqiao He commented on HDFS-15391: This issue is duplicated by HDFS-15175, will close this one.

[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=17135675#comment-17135675 ] Xiaoqiao He edited comment on HDFS-15175 at 6/15/20, 9:42 AM: -- Add

[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=17135675#comment-17135675 ] Xiaoqiao He commented on HDFS-15175: Add [~wanchang] as contributor and assign this issue to him. >

[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=17135722#comment-17135722 ] Xiaoqiao He commented on HDFS-15175: Thanks [~wanchang] for the patch. It is almost LGTM, adding ut

[jira] [Resolved] (HDFS-15391) Standby NameNode due loads the corruption edit log, the service exits and cannot be restarted

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-15391. Resolution: Duplicate > Standby NameNode due loads the corruption edit log, the service exits and

[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=17135675#comment-17135675 ] Xiaoqiao He edited comment on HDFS-15175 at 6/15/20, 9:43 AM: -- Add

[jira] [Commented] (HDFS-15390) client fails forever when namenode ipaddr changed

[ https://issues.apache.org/jira/browse/HDFS-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127894#comment-17127894 ] Xiaoqiao He commented on HDFS-15390: [~seanlook], It is great catch here. Some nits, a. This ticket

[jira] [Created] (HDFS-15397) Blocks recovery could overwhelm KDC when using Kerberos for authentication

Xiaoqiao He created HDFS-15397: -- Summary: Blocks recovery could overwhelm KDC when using Kerberos for authentication Key: HDFS-15397 URL: https://issues.apache.org/jira/browse/HDFS-15397 Project: Hadoop

[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.001.patch Status: Patch Available (was: Open) submit demo patch and

[jira] [Commented] (HDFS-15391) Standby NameNode due loads the corruption edit log, the service exits and cannot be restarted

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17133315#comment-17133315 ] Xiaoqiao He commented on HDFS-15391: Hi [~haiyang Hu], Do you enable AsyncEditlog feature? I think it

[jira] [Commented] (HDFS-12733) Option to disable to namenode local edits

[ https://issues.apache.org/jira/browse/HDFS-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132544#comment-17132544 ] Xiaoqiao He commented on HDFS-12733: Thanks [~ayushtkn] for your reviews. {quote}This block could

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158875#comment-17158875 ] Xiaoqiao He commented on HDFS-14498: Thanks [~Jim_Brennan],[~sodonnell], {quote}there are multiple

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14498: --- Attachment: HDFS-14498-branch-2.10.003.patch > LeaseManager can loop forever on the file for which

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14498: --- Fix Version/s: 3.1.5 2.10.1 3.2.2 Resolution: Fixed

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159331#comment-17159331 ] Xiaoqiao He commented on HDFS-14498: +1. Commit to branch-3.2/branch-3.1/branch-2.10. Thanks

[jira] [Updated] (HDFS-15451) Restarting name node stuck in safe mode when using provided storage

[ https://issues.apache.org/jira/browse/HDFS-15451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15451: --- Fix Version/s: 3.1.5 3.3.1 3.2.2 > Restarting name node stuck

[jira] [Updated] (HDFS-15451) Restarting name node stuck in safe mode when using provided storage

[ https://issues.apache.org/jira/browse/HDFS-15451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15451: --- Affects Version/s: (was: 3.1.3) (was: 3.2.1) > Restarting name node

[jira] [Commented] (HDFS-15451) Restarting name node stuck in safe mode when using provided storage

[ https://issues.apache.org/jira/browse/HDFS-15451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152470#comment-17152470 ] Xiaoqiao He commented on HDFS-15451: cherrypick to branch-3.3, branch-3.2 and branch-3.1. Thanks

[jira] [Commented] (HDFS-15769) Metric metadataOperationRate maybe incorrect

[ https://issues.apache.org/jira/browse/HDFS-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17262625#comment-17262625 ] Xiaoqiao He commented on HDFS-15769: Thanks [~xuzq_zander] for your quick response. It makes sense to

[jira] [Commented] (HDFS-15769) Metric metadataOperationRate maybe incorrect

[ https://issues.apache.org/jira/browse/HDFS-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17262610#comment-17262610 ] Xiaoqiao He commented on HDFS-15769: Thanks [~xuzq_zander] for your report. cc [~Aiphag0] Please take

[jira] [Commented] (HDFS-15680) Disable Broken Azure Junits

[ https://issues.apache.org/jira/browse/HDFS-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239599#comment-17239599 ] Xiaoqiao He commented on HDFS-15680: Thanks [~ste...@apache.org], IIUC, if we backport HADOOP-17325

[jira] [Commented] (HDFS-15680) Disable Broken Azure Junits

[ https://issues.apache.org/jira/browse/HDFS-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17240838#comment-17240838 ] Xiaoqiao He commented on HDFS-15680: Thanks [~ayushtkn] for your informations. I backport

[jira] [Commented] (HDFS-14437) Exception happened when rollEditLog expects empty EditsDoubleBuffer.bufCurrent but not

[ https://issues.apache.org/jira/browse/HDFS-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17240663#comment-17240663 ] Xiaoqiao He commented on HDFS-14437: [~Sushma_28] Actually, I also meet the similar case (NameNode

[jira] [Commented] (HDFS-15684) EC: Call recoverLease on DFSStripedOutputStream close exception

[ https://issues.apache.org/jira/browse/HDFS-15684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17236597#comment-17236597 ] Xiaoqiao He commented on HDFS-15684: trigger Jenkins manually and let see what it says. > EC: Call

[jira] [Commented] (HDFS-15680) Disable Broken Azure Junits

[ https://issues.apache.org/jira/browse/HDFS-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239149#comment-17239149 ] Xiaoqiao He commented on HDFS-15680: [~ste...@apache.org], Just found that HADOOP-17325 has resolved

[jira] [Updated] (HDFS-15708) TestURLConnectionFactory fails by NoClassDefFoundError in branch-3.3 and branch-3.2

[ https://issues.apache.org/jira/browse/HDFS-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15708: --- Fix Version/s: 3.2.3 cherry-pick to branch-3.2.2. > TestURLConnectionFactory fails by

[jira] [Updated] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15240: --- Fix Version/s: 3.2.2 > Erasure Coding: dirty buffer causes reconstruction block error >

[jira] [Commented] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244406#comment-17244406 ] Xiaoqiao He commented on HDFS-15240: cherry-pick to branch-3.2.2. > Erasure Coding: dirty buffer

[jira] [Updated] (HDFS-15709) EC: Socket file descriptor leak in StripedBlockChecksumReconstructor

[ https://issues.apache.org/jira/browse/HDFS-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15709: --- Fix Version/s: 3.2.2 cherry-pick to branch-3.2.2 > EC: Socket file descriptor leak in

[jira] [Updated] (HDFS-15707) NNTop counts don't add up as expected

[ https://issues.apache.org/jira/browse/HDFS-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15707: --- Fix Version/s: 3.2.2 cherry-pick to branch-3.2.2. > NNTop counts don't add up as expected >

[jira] [Commented] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246530#comment-17246530 ] Xiaoqiao He commented on HDFS-15170: Sorry, I do not read above comment carefully, it makes sense to

[jira] [Commented] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246483#comment-17246483 ] Xiaoqiao He commented on HDFS-15170: OK, Thanks for your information, get it. Let's backport to the

[jira] [Created] (HDFS-15723) RBF: invokeConcurrent may run unexpected when enable standby read

Xiaoqiao He created HDFS-15723: -- Summary: RBF: invokeConcurrent may run unexpected when enable standby read Key: HDFS-15723 URL: https://issues.apache.org/jira/browse/HDFS-15723 Project: Hadoop HDFS

[jira] [Updated] (HDFS-15723) RBF: invokeConcurrent may run unexpected when enable standby read

[ https://issues.apache.org/jira/browse/HDFS-15723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15723: --- Attachment: HDFS-15723.001.patch Assignee: Xiaoqiao He Status: Patch Available (was:

[jira] [Updated] (HDFS-15723) RBF: invokeConcurrent may run unexpected when enable standby read

[ https://issues.apache.org/jira/browse/HDFS-15723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15723: --- Description: My colleague report that the following code segment has wrong parameter passed when

[jira] [Commented] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246450#comment-17246450 ] Xiaoqiao He commented on HDFS-15170: [~ayushtkn] Thanks for your works here. IMO, this issue could

[jira] [Updated] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15240: --- Target Version/s: 3.2.2, 3.3.1, 3.4.0, 3.1.5, 3.2.3 (was: 3.3.1, 3.4.0, 3.1.5, 3.2.3) > Erasure

[jira] [Updated] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15240: --- Attachment: HDFS-15240-branch-3.2.001.patch > Erasure Coding: dirty buffer causes reconstruction

[jira] [Reopened] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He reopened HDFS-15240: > Erasure Coding: dirty buffer causes reconstruction block error >

[jira] [Updated] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15240: --- Status: Patch Available (was: Reopened) > Erasure Coding: dirty buffer causes reconstruction block

[jira] [Commented] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17243887#comment-17243887 ] Xiaoqiao He commented on HDFS-15240: reopen and add 3.2.2 as another target version. upload

[jira] [Commented] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244039#comment-17244039 ] Xiaoqiao He commented on HDFS-15240: It seems failed unit test is not related with this issue. check

[jira] [Updated] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15240: --- Fix Version/s: 3.2.3 > Erasure Coding: dirty buffer causes reconstruction block error >

[jira] [Commented] (HDFS-15732) EC client will not retry get block token when block token expired in kerberized cluster

[ https://issues.apache.org/jira/browse/HDFS-15732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251084#comment-17251084 ] Xiaoqiao He commented on HDFS-15732: Hi [~lalapala], Thanks for your report. IMO, I think it is about

[jira] [Commented] (HDFS-15746) Standby NameNode crash when replay editlog

[ https://issues.apache.org/jira/browse/HDFS-15746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17254400#comment-17254400 ] Xiaoqiao He commented on HDFS-15746: Thanks [~elgoiri] and [~shv] for your suggestions, Sound good to

[jira] [Created] (HDFS-15746) Standby NameNode crash when replay editlog

Xiaoqiao He created HDFS-15746: -- Summary: Standby NameNode crash when replay editlog Key: HDFS-15746 URL: https://issues.apache.org/jira/browse/HDFS-15746 Project: Hadoop HDFS Issue Type: Bug

[jira] [Updated] (HDFS-15746) Standby NameNode crash when replay editlog

[ https://issues.apache.org/jira/browse/HDFS-15746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15746: --- Attachment: HDFS-15746.001.patch > Standby NameNode crash when replay editlog >

[jira] [Updated] (HDFS-15746) Standby NameNode crash when replay editlog

[ https://issues.apache.org/jira/browse/HDFS-15746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15746: --- Status: Patch Available (was: Open) > Standby NameNode crash when replay editlog >

[jira] [Updated] (HDFS-15478) When Empty mount points, we are assigning fallback link to self. But it should not use full URI for target fs.

[ https://issues.apache.org/jira/browse/HDFS-15478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15478: --- Fix Version/s: 3.2.3 3.2.2 Add fix version 3.2.2 + 3.2.3, Please update fix

[jira] [Updated] (HDFS-15574) Remove unnecessary sort of block list in DirectoryScanner

[ https://issues.apache.org/jira/browse/HDFS-15574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15574: --- Fix Version/s: 3.2.2 Add fix version 3.2.2 + 3.2.3, Please update fix version tag in time when

[jira] [Updated] (HDFS-15567) [SBN Read] HDFS should expose msync() API to allow downstream applications call it explicitly.

[ https://issues.apache.org/jira/browse/HDFS-15567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15567: --- Fix Version/s: 3.2.2 > [SBN Read] HDFS should expose msync() API to allow downstream applications >

[jira] [Updated] (HDFS-15583) Backport DirectoryScanner improvements HDFS-14476, HDFS-14751 and HDFS-15048 to branch 3.2 and 3.1

[ https://issues.apache.org/jira/browse/HDFS-15583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15583: --- Fix Version/s: 3.2.2 Add fix version 3.2.2 + 3.2.3, Please update fix version tag in time when

[jira] [Updated] (HDFS-15628) HttpFS server throws NPE if a file is a symlink

[ https://issues.apache.org/jira/browse/HDFS-15628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15628: --- Fix Version/s: 3.2.2 Add fix version 3.2.2 + 3.2.3, Please update fix version tag in time when

[jira] [Updated] (HDFS-15464) ViewFsOverloadScheme should work when -fs option pointing to remote cluster without mount links

[ https://issues.apache.org/jira/browse/HDFS-15464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15464: --- Fix Version/s: 3.2.3 3.2.2 Add fix version 3.2.2 + 3.2.3, Please update fix

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