Thanks Wei-Chiu,
I feel now IBR is more stable in branch 3.x. If BR is just added to prevent
bugs in IBR, I feel we should fix such bug in IBR. Adding one new
functionality to prevent bug in other is not good.
I also thing, DN should send BR in failure and process start scenario only.
-Surendra
Hi Wei-Chiu,
Thanx for the response.
Yes, We are talking about the FBR only.
Increasing the frequency limits the problem, but doesn’t seems to be solving
it. With increasing cluster size, the frequency needs to be increased, and we
cannot increase it indefinitely, as in some case FBR is needed.
O
Hey Ayush,
Thanks a lot for your proposal.
Do you mean the Full Block Report that is sent out every 6 hours per
DataNode?
Someone told me they reduced the frequency of FBR to 24 hours and it seems
okay.
One of the purposes of FBR was to prevent bugs in incremental block report
implementation. In
Aravindan Vijayan created HDFS-15156:
Summary: In-Place Erasure Coding should factor in storage quota
validations.
Key: HDFS-15156
URL: https://issues.apache.org/jira/browse/HDFS-15156
Project: H
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1403/
[Feb 5, 2020 1:44:05 AM] (jhung) YARN-10116. Expose diagnostics in RMAppManager
summary
-1 overall
The following subsystems voted -1:
asflicense findbugs pathlen unit xml
The following subsyste
Haibin Huang created HDFS-15155:
---
Summary: writeIoRate of DataNodeVolumeMetrics is never used
Key: HDFS-15155
URL: https://issues.apache.org/jira/browse/HDFS-15155
Project: Hadoop HDFS
Issue Ty
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/589/
[Feb 5, 2020 7:16:09 PM] (jhung) YARN-10116. Expose diagnostics in RMAppManager
summary
[Feb 5, 2020 7:33:30 PM] (kihwal) HADOOP-15787.
TestIPC.testRTEDuringConnectionSetup fails with jdk8u242.
-
