[jira] [Commented] (HDFS-17024) Potential data race introduced by HDFS-15865

[ https://issues.apache.org/jira/browse/HDFS-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780172#comment-17780172 ] ASF GitHub Bot commented on HDFS-17024: --- aajisaka commented on PR #6223: URL:

[jira] [Updated] (HDFS-17024) Potential data race introduced by HDFS-15865

[ https://issues.apache.org/jira/browse/HDFS-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-17024: --- Fix Version/s: 3.3.9 > Potential data race introduced by HDFS-15865 >

[jira] [Assigned] (HDFS-17024) Potential data race introduced by HDFS-15865

[ https://issues.apache.org/jira/browse/HDFS-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang reassigned HDFS-17024: -- Assignee: Segawa Hiroaki > Potential data race introduced by HDFS-15865 >

[jira] [Resolved] (HDFS-17024) Potential data race introduced by HDFS-15865

[ https://issues.apache.org/jira/browse/HDFS-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang resolved HDFS-17024. Fix Version/s: 3.4.0 Resolution: Fixed > Potential data race introduced by

[jira] [Commented] (HDFS-17024) Potential data race introduced by HDFS-15865

[ https://issues.apache.org/jira/browse/HDFS-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780171#comment-17780171 ] ASF GitHub Bot commented on HDFS-17024: --- jojochuang merged PR #6223: URL:

[jira] [Assigned] (HDFS-17024) Potential data race introduced by HDFS-15865

[ https://issues.apache.org/jira/browse/HDFS-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang reassigned HDFS-17024: -- Assignee: (was: Wei-Chiu Chuang) > Potential data race introduced by HDFS-15865 >

[jira] [Updated] (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:all-tabpanel ] shuaiqi.guo updated HDFS-17241: --- Description: when standby NN triggering log roll on active NN and sending fsimage to active NN at

[jira] [Updated] (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:all-tabpanel ] shuaiqi.guo updated HDFS-17241: --- Description: when standby NN triggering log roll on active NN and sending fsimage to active NN at

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

shuaiqi.guo created HDFS-17241: -- Summary: long write lock on active NN from rollEditLog() Key: HDFS-17241 URL: https://issues.apache.org/jira/browse/HDFS-17241 Project: Hadoop HDFS Issue Type:

[jira] [Commented] (HDFS-17063) Datanode configures different Capacity Reserved for each disk

[ https://issues.apache.org/jira/browse/HDFS-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780140#comment-17780140 ] ASF GitHub Bot commented on HDFS-17063: --- qijiale76 commented on PR #5793: URL:

[jira] [Commented] (HDFS-17024) Potential data race introduced by HDFS-15865

[ https://issues.apache.org/jira/browse/HDFS-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780123#comment-17780123 ] ASF GitHub Bot commented on HDFS-17024: --- aajisaka commented on PR #6223: URL:

[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=17780041#comment-17780041 ] Wei-Chiu Chuang commented on HDFS-15273: +1 sorry for the very late review. IMO the second sleep

[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 ] Wei-Chiu Chuang updated HDFS-15273: --- Fix Version/s: 3.4.0 Resolution: Fixed Status: Resolved (was: Patch

[jira] [Commented] (HDFS-17232) RBF: Fix NoNamenodesAvailableException for a long time, when use observer

[ https://issues.apache.org/jira/browse/HDFS-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780040#comment-17780040 ] ASF GitHub Bot commented on HDFS-17232: --- hadoop-yetus commented on PR #6208: URL:

[jira] [Commented] (HDFS-16849) Terminate SNN when failing to perform EditLogTailing

[ https://issues.apache.org/jira/browse/HDFS-16849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780007#comment-17780007 ] Srinivasu Majeti commented on HDFS-16849: - CCing [~weichiu] to review this . > Terminate SNN

[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=17780003#comment-17780003 ] Srinivasu Majeti commented on HDFS-15273: - CCing [~weichiu] to review this and approve. >

[jira] [Commented] (HDFS-17240) Fix a typo in DataStorage.java

[ https://issues.apache.org/jira/browse/HDFS-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780002#comment-17780002 ] ASF GitHub Bot commented on HDFS-17240: --- yuw1 opened a new pull request, #6226: URL:

[jira] [Updated] (HDFS-17240) Fix a typo in DataStorage.java

[ https://issues.apache.org/jira/browse/HDFS-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDFS-17240: -- Labels: pull-request-available (was: ) > Fix a typo in DataStorage.java >

[jira] [Commented] (HDFS-16950) Gap in edits after -initializeSharedEdits

[ https://issues.apache.org/jira/browse/HDFS-16950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780001#comment-17780001 ] Wei-Chiu Chuang commented on HDFS-16950: Karthik said because of the missing edit logs it caused

[jira] [Created] (HDFS-17240) Fix a typo in DataStorage.java

Yu Wang created HDFS-17240: -- Summary: Fix a typo in DataStorage.java Key: HDFS-17240 URL: https://issues.apache.org/jira/browse/HDFS-17240 Project: Hadoop HDFS Issue Type: Bug Components:

[jira] [Updated] (HDFS-16950) Gap in edits after -initializeSharedEdits

[ https://issues.apache.org/jira/browse/HDFS-16950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-16950: --- Priority: Critical (was: Major) > Gap in edits after -initializeSharedEdits >

[jira] [Updated] (HDFS-16950) Gap in edits after -initializeSharedEdits

[ https://issues.apache.org/jira/browse/HDFS-16950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-16950: --- Issue Type: Bug (was: Improvement) > Gap in edits after -initializeSharedEdits >

[jira] [Commented] (HDFS-17239) Remove logging of method removeReplicaFromMem which is in BLOCK_POOl write lock.

[ https://issues.apache.org/jira/browse/HDFS-17239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779965#comment-17779965 ] ASF GitHub Bot commented on HDFS-17239: --- hadoop-yetus commented on PR #6225: URL:

[jira] [Commented] (HDFS-17239) Remove logging of method removeReplicaFromMem which is in BLOCK_POOl write lock.

[ https://issues.apache.org/jira/browse/HDFS-17239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779963#comment-17779963 ] ASF GitHub Bot commented on HDFS-17239: --- hadoop-yetus commented on PR #6225: URL:

[jira] [Commented] (HDFS-17232) RBF: Fix NoNamenodesAvailableException for a long time, when use observer

[ https://issues.apache.org/jira/browse/HDFS-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779946#comment-17779946 ] ASF GitHub Bot commented on HDFS-17232: --- KeeProMise commented on code in PR #6208: URL:

[jira] [Updated] (HDFS-17239) Remove logging of method removeReplicaFromMem which is in BLOCK_POOl write lock.

[ https://issues.apache.org/jira/browse/HDFS-17239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDFS-17239: -- Labels: pull-request-available (was: ) > Remove logging of method removeReplicaFromMem which

[jira] [Commented] (HDFS-17239) Remove logging of method removeReplicaFromMem which is in BLOCK_POOl write lock.

[ https://issues.apache.org/jira/browse/HDFS-17239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779817#comment-17779817 ] ASF GitHub Bot commented on HDFS-17239: --- hfutatzhanghb opened a new pull request, #6225: URL:

[jira] [Commented] (HDFS-17239) Remove logging of method removeReplicaFromMem which is in BLOCK_POOl write lock.

[ https://issues.apache.org/jira/browse/HDFS-17239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779796#comment-17779796 ] farmmamba commented on HDFS-17239: -- [~haiyang Hu] Sir, what's your opinions？ Thanks. > Remove logging

[jira] [Updated] (HDFS-17239) Remove logging of method removeReplicaFromMem which is in BLOCK_POOl write lock.

[ https://issues.apache.org/jira/browse/HDFS-17239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] farmmamba updated HDFS-17239: - Description: In method FsDatasetImpl#removeReplicaFromMem,  there exists some loggings in the range of

[jira] [Updated] (HDFS-17239) Remove logging of method removeReplicaFromMem which is in BLOCK_POOl write lock.

[ https://issues.apache.org/jira/browse/HDFS-17239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] farmmamba updated HDFS-17239: - Summary: Remove logging of method removeReplicaFromMem which is in BLOCK_POOl write lock. (was: Remove

[jira] [Commented] (HDFS-17238) Setting the value of "dfs.blocksize" too large will cause HDFS to be unable to write to files

[ https://issues.apache.org/jira/browse/HDFS-17238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779789#comment-17779789 ] Jim Halfpenny commented on HDFS-17238: -- In your example you've set dfs.blocksize to 1.25 TiB, a

[jira] [Commented] (HDFS-17239) Remove logging of method invalidate which is in BLOCK_POOl write lock.

[ https://issues.apache.org/jira/browse/HDFS-17239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779785#comment-17779785 ] farmmamba commented on HDFS-17239: -- [~hexiaoqiao] [~zhangshuyan]  [~tomscut]  [~qinyuren]  Sir, could

[jira] [Created] (HDFS-17239) Remove logging of method invalidate which is in BLOCK_POOl write lock.

farmmamba created HDFS-17239: Summary: Remove logging of method invalidate which is in BLOCK_POOl write lock. Key: HDFS-17239 URL: https://issues.apache.org/jira/browse/HDFS-17239 Project: Hadoop HDFS

[jira] [Updated] (HDFS-17238) Setting the value of "dfs.blocksize" too large will cause HDFS to be unable to write to files

[ https://issues.apache.org/jira/browse/HDFS-17238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ECFuzz updated HDFS-17238: -- Description: My hadoop version is 3.3.6, and I use the Pseudo-Distributed Operation. core-site.xml like

[jira] [Updated] (HDFS-17238) Setting the value of "dfs.blocksize" too large will cause HDFS to be unable to write to files

[ https://issues.apache.org/jira/browse/HDFS-17238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ECFuzz updated HDFS-17238: -- Description: My hadoop version is 3.3.6, and I use the Pseudo-Distributed Operation. core-site.xml like

[jira] [Updated] (HDFS-17238) Setting the value of "dfs.blocksize" too large will cause HDFS to be unable to write to files

[ https://issues.apache.org/jira/browse/HDFS-17238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ECFuzz updated HDFS-17238: -- Description: My hadoop version is 3.3.6, and I use the Pseudo-Distributed Operation. core-site.xml like

[jira] [Updated] (HDFS-17238) Setting the value of "dfs.blocksize" too large will cause HDFS to be unable to write to files

[ https://issues.apache.org/jira/browse/HDFS-17238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ECFuzz updated HDFS-17238: -- Description: My hadoop version is 3.3.6, and I use the Pseudo-Distributed Operation. core-site.xml like

[jira] [Updated] (HDFS-17069) The documentation and implementation of "dfs.blocksize" are inconsistent.

[ https://issues.apache.org/jira/browse/HDFS-17069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ECFuzz updated HDFS-17069: -- Description: My hadoop version is 3.3.6, and I use the Pseudo-Distributed Operation. core-site.xml like

[jira] [Updated] (HDFS-17238) Setting the value of "dfs.blocksize" too large will cause HDFS to be unable to write to files

[ https://issues.apache.org/jira/browse/HDFS-17238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ECFuzz updated HDFS-17238: -- Description: My hadoop version is 3.3.6, and I use the Pseudo-Distributed Operation. core-site.xml like

[jira] [Created] (HDFS-17238) Setting the value of "dfs.blocksize" too large will cause HDFS to be unable to write to files

ECFuzz created HDFS-17238: - Summary: Setting the value of "dfs.blocksize" too large will cause HDFS to be unable to write to files Key: HDFS-17238 URL: https://issues.apache.org/jira/browse/HDFS-17238