[jira] [Created] (HDFS-15705) Fix a typo in SecondaryNameNode.java

Sixiang Ma created HDFS-15705: - Summary: Fix a typo in SecondaryNameNode.java Key: HDFS-15705 URL: https://issues.apache.org/jira/browse/HDFS-15705 Project: Hadoop HDFS Issue Type: Bug

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC3

Thanks Xiaoqiao for the work! Unfortunately we just discovered an issue (HADOOP-16080) which prevents Spark from consuming this release. I'm working on a PR for this and wondering if we can include the fix in the release too. Thanks again and apologies for the late notice. Best, Chao On Mon, Nov

Apache Hadoop qbt Report: trunk+JDK11 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/76/ [Dec 1, 2020 9:02:53 PM] (noreply) HDFS-15694. Avoid calling UpdateHeartBeatState inside DataNodeDescriptor. (#2487) Contributed by Kuhu Shukla and Ahmed Hussein [Dec 1, 2020 10:06:47 PM] (Eric Payne

Re: FSImage size issue

The heap histo does show it is caused by snapshot 2: 36069513725970049864 org.apache.hadoop.hdfs.server.namenode.INodeFileAttributes$SnapshotCopy 3: 36069513720198927672 org.apache.hadoop.hdfs.server.namenode.snapshot.FileDiff 4: 36345766311630645216 org.apache.hadoop.

Re: FSImage size issue

I also suspect it might be caused by snapshots. We don't have lots of xattr or ALCs on our files. How can I confirm if it is really caused by snapshots? Thanks, Jason On 12/1/20, 4:43 PM, "Wei-Chiu Chuang" wrote: Possibly snapshots. Also possible if each of your files has lots of xatt

Re: FSImage size issue

Possibly snapshots. Also possible if each of your files has lots of xattr or ACLs. On Tue, Dec 1, 2020 at 3:52 PM Jason Wen wrote: > Hi, > > We are encountering some odd FSImage size issue in one of our Hadoop > clusters. The Namenode only has about 3M files/blocks, but the FSImage size > is abo

FSImage size issue

Hi, We are encountering some odd FSImage size issue in one of our Hadoop clusters. The Namenode only has about 3M files/blocks, but the FSImage size is about 55GB. We have never seen this kind of gap between number of files/blocks vs FSImage size. As a comparison, we have another similar cluster

[jira] [Resolved] (HDFS-15694) Avoid calling UpdateHeartBeatState inside DataNodeDescriptor

[ https://issues.apache.org/jira/browse/HDFS-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan resolved HDFS-15694. Fix Version/s: 3.2.3 3.1.5 3.4.0 3.3.1

Unable to close file because the last block does not have enough number of replicas.

Hi folks, We did the HDFS namenode swap with the same name but different ip address so the clients don't need to change the configuration. While after that some applications are seeing "Unable to close file because the last block does not have enough number of replicas." and server side sees "org.

[jira] [Created] (HDFS-15704) Mitigate lease monitor's rapid infinite loop

Ahmed Hussein created HDFS-15704: Summary: Mitigate lease monitor's rapid infinite loop Key: HDFS-15704 URL: https://issues.apache.org/jira/browse/HDFS-15704 Project: Hadoop HDFS Issue Type:

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/342/ [Nov 30, 2020 2:17:10 AM] (noreply) YARN-10498. Fix typo in CapacityScheduler Markdown document (#2484) [Nov 30, 2020 6:53:54 AM] (noreply) HDFS-15699 Remove lz4 references in vcxproj (#2498) [Nov 30

[jira] [Created] (HDFS-15703) Don't generate edits for set operations that are no-op

Ahmed Hussein created HDFS-15703: Summary: Don't generate edits for set operations that are no-op Key: HDFS-15703 URL: https://issues.apache.org/jira/browse/HDFS-15703 Project: Hadoop HDFS Is