Re: Restrict Frequency of BlockReport To Namenode startup and failover
Hi Stephen, We are trying this on 3.1.1 We aren’t upgrading from 2.x, we are trying to increase the cluster size to go beyond 10K datanodes. In the process, we analysed that block reports from these many DN’s are quite bothersome. There are plenty of reasons why block reports bothers performance, the major being namenode holding the lock for these many datanodes, as you mentioned. HDFS-14657 may improve the situation a bit(I didn’t follow it) but our point is rather than improving the impact, we can completely get rid of them in most of the cases. Why to unnecessarily have load of processing Block Reports, if it isn’t doing anything good. So, just wanted to know, if people are aware of any cases where eliminating regular BR’s can be a problem, which we might have missed. Let me know if you possess hard feelings for the change or doubt something. -Ayush > On 07-Feb-2020, at 4:03 PM, Stephen O'Donnell wrote: > > > Are you seeing this problem on the 3.x branch, and if so, did the problem > exist before you upgraded to 3.x? I am wondering if the situation is better > or worse since moving to 3.x. > > Also, do you believe the issue is driven by the namenode holding its lock for > too long while it processes each block report, blocking other threads? > > There was an interesting proposal in > https://issues.apache.org/jira/browse/HDFS-14657 to allow the NN lock to be > dropped and retaken periodically while processing FBRs, but it has not > progressed recently. I wonder if that would help here? > > Thanks, > > Stephen. > >> On Fri, Feb 7, 2020 at 6:58 AM Surendra Singh Lilhore >> wrote: >> 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 >> >> On Fri, Feb 7, 2020 at 10:52 AM Ayush Saxena wrote: >> >> > 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. >> > One such case is Namenode failover, In case of failover the namenode marks >> > all the storages as Stale, it would correct them only once FBR comes, Any >> > overreplicated blocks won’t be deleted until the storages are in stale >> > state. >> > >> > Regarding the IBR error, the block is set Completed post IBR, when the >> > client claimed value and IBR values matches, so if there is a discrepancy >> > here, it would alarm out there itself. >> > >> > If it passes over this spot, so the FBR would also be sending the same >> > values from memory, it doesn’t check from the actual disk. >> > DirectoryScanner would be checking if the in memory data is same as that >> > on the disk. >> > Other scenario where FBR could be needed is to counter a split brain >> > scenario, but with QJM’s that is unlikely to happen. >> > >> > In case of any connection losses during the interval, we tend to send the >> > BR, so should be safe here. >> > >> > Anyway if a client gets hold of a invalid block, it will too report to the >> > Namenode. >> > >> > Other we cannot think as such, where not sending FBR can cause any issue. >> > >> > Let us know your thoughts on this.. >> > >> > -Ayush >> > >> > >>> On 07-Feb-2020, at 4:12 AM, Wei-Chiu Chuang >> > wrote: >> > >> 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 other words, it's a fail-safe mechanism. Any bugs in >> > >> IBRs get corrected after a FBR that refreshes the state of blocks at >> > >> NameNode. At least, that's my understanding of FBRs in its early days. >> > >> >> > >> On Tue, Feb 4, 2020 at 12:21 AM Ayush Saxena >> > wrote: >> > >> >> > >> Hi All, >> > >> Me and Surendra have been lately trying to minimise the impact of Block >> > >> Reports on Namenode in huge cluster. We observed in a huge cluster, >> > about >> > >> 10k datanodes, the periodic block reports impact the Namenode >> > performance >> > >> adversely. >> > >> We have been thinking to restrict the block reports to be triggered only >> > >> during Namenode startup or in case of failover and eliminate the >> > periodic >> > >> block report. >> > >> The main purpose of block report is to get a corrupt blocks recognised, >> > so >> > >> as a follow up we can maintain a service at datanode to run >> > periodically to >> > >> check if the block size in mem
Apache Hadoop qbt Report: branch2.10+JDK7 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/ No changes -1 overall The following subsystems voted -1: asflicense findbugs hadolint pathlen unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: XML : Parsing Error(s): hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/empty-configuration.xml hadoop-tools/hadoop-azure/src/config/checkstyle-suppressions.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/public/crossdomain.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml FindBugs : module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client Boxed value is unboxed and then immediately reboxed in org.apache.hadoop.yarn.server.timelineservice.storage.common.ColumnRWHelper.readResultsWithTimestamps(Result, byte[], byte[], KeyConverter, ValueConverter, boolean) At ColumnRWHelper.java:then immediately reboxed in org.apache.hadoop.yarn.server.timelineservice.storage.common.ColumnRWHelper.readResultsWithTimestamps(Result, byte[], byte[], KeyConverter, ValueConverter, boolean) At ColumnRWHelper.java:[line 335] Failed junit tests : hadoop.hdfs.server.namenode.ha.TestDelegationTokensWithHA hadoop.hdfs.qjournal.server.TestJournalNodeRespectsBindHostKeys hadoop.hdfs.server.namenode.TestNameNodeHttpServerXFrame hadoop.contrib.bkjournal.TestBookKeeperHACheckpoints hadoop.contrib.bkjournal.TestBookKeeperHACheckpoints hadoop.registry.secure.TestSecureLogins hadoop.yarn.server.nodemanager.amrmproxy.TestFederationInterceptor hadoop.yarn.server.timelineservice.security.TestTimelineAuthFilterForV2 cc: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-compile-cc-root-jdk1.7.0_95.txt [4.0K] javac: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-compile-javac-root-jdk1.7.0_95.txt [328K] cc: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-compile-cc-root-jdk1.8.0_242.txt [4.0K] javac: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-compile-javac-root-jdk1.8.0_242.txt [308K] checkstyle: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-checkstyle-root.txt [16M] hadolint: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-patch-hadolint.txt [4.0K] pathlen: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/pathlen.txt [12K] pylint: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-patch-pylint.txt [24K] shellcheck: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-patch-shellcheck.txt [56K] shelldocs: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-patch-shelldocs.txt [8.0K] whitespace: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/whitespace-eol.txt [12M] https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/whitespace-tabs.txt [1.3M] xml: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/xml.txt [12K] findbugs: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice-hbase_hadoop-yarn-server-timelineservice-hbase-client-warnings.html [8.0K] javadoc: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-javadoc-javadoc-root-jdk1.7.0_95.txt [16K] https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/diff-javadoc-javadoc-root-jdk1.8.0_242.txt [1.1M] unit: https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt [236K] https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs_src_contrib_bkjournal.txt [12K] https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/591/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-regis
Re: Why capacity scheduler not support DRF?
Thanks @epayne for your response, actually, i wonder why do not support sort based on DRF like FairScheduler. epa...@apache.org 于2020年2月8日周六 上午5:39写道： > Hi, > > I didn't see anyone respond to your question. If you already got a > response, > please ignore this one. > > The Capacity Scheduler does support DRF. You can specify which resource > calculator to use by setting the > yarn.scheduler.capacity.resource-calculator > property: > > > yarn.scheduler.capacity.resource-calculator > > org.apache.hadoop.yarn.util.resource.DominantResourceCalculator > > > The DefaultResourceCalculator is set by default. So if you want the DRF, > you > need to set the resource-calculator property as shown above. > > Hope that helps, > -Eric > > On Friday, January 31, 2020, 5:04:57 AM CST, 周康 > wrote: > > Why capacity scheduler not support DRF? > Since FairScheduler support > > -- > 祝好, > 周康 > -- 祝好, 周康
[jira] [Created] (HADOOP-16848) add initial S3A layering + async init
Steve Loughran created HADOOP-16848: --- Summary: add initial S3A layering + async init Key: HADOOP-16848 URL: https://issues.apache.org/jira/browse/HADOOP-16848 Project: Hadoop Common Issue Type: Sub-task Components: fs/s3 Affects Versions: 3.3.0 Reporter: Steve Loughran Assignee: Steve Loughran Split the S3A code into layers * S3AFileSystem * S3AStore + Impl * RawS3A + Impl S3AFS will create the others and start in order: DelegationTokens, RawS3A, S3AStore, Metastore this will involve wrapping all access of DTs, s3client, Metastore to block until that layer is complete, or raise an exception if instantiation of it/predecessor failed. New layers will all be subclasses of Service, split into Interface and Impl, so we can manage the init/start/stop lifecycle with existing code -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1406/ [Feb 9, 2020 1:44:18 PM] (ayushsaxena) YARN-9624. Use switch case for ProtoUtils#convertFromProtoFormat [Feb 9, 2020 3:44:53 PM] (sunilg) YARN-10109. Allow stop and convert from leaf to parent queue in a single [Feb 9, 2020 6:02:22 PM] (ayushsaxena) HDFS-15158. The number of failed volumes mismatch with volumeFailures of - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
