[
https://issues.apache.org/jira/browse/HDFS-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Prakash updated HDFS-8763:
---
Description:
- For our cluster, the NameNode is always very busy, so for every incremental
block
[
https://issues.apache.org/jira/browse/HDFS-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo Nicholas Sze updated HDFS-8763:
--
Component/s: (was: HDFS)
> After file closed, a race condition between IBR of 3rd
[
https://issues.apache.org/jira/browse/HDFS-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walter Su updated HDFS-8763:
Status: Open (was: Patch Available)
> After file closed, a race condition between IBR of 3rd replica of
[
https://issues.apache.org/jira/browse/HDFS-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walter Su updated HDFS-8763:
Attachment: HDFS-8763.02.patch
bq. We occasionally see the same issue, but not frequent enough to be a
[
https://issues.apache.org/jira/browse/HDFS-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walter Su updated HDFS-8763:
Description:
-For our cluster, the NameNode is always very busy, so for every incremental
block report ,
[
https://issues.apache.org/jira/browse/HDFS-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walter Su updated HDFS-8763:
Summary: After file closed, a race condition between IBR of 3rd replica of
lastBlock and ReplicationMonitor
