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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1483/ [Apr 27, 2020 6:26:11 AM] (snemeth) YARN-10194. YARN RMWebServices /scheduler-conf/validate leaks ZK [Apr 27, 2020 8:20:47 AM] (github) HDFS-15298 Fix the findbugs warnings introduced in HDFS-15217 (#1979

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/669/ [Apr 27, 2020 9:14:42 PM] (jhung) YARN-8382. cgroup file leak in NM. Contributed by Hu Ziqian. [Apr 28, 2020 12:14:21 AM] (ericp) MAPREDUCE-7277. IndexCache totalMemoryUsed differs from cache content

[jira] [Created] (HDFS-15303) Provide a tool that can validate/fix the block file placement in DataNode data directories

Istvan Fajth created HDFS-15303: --- Summary: Provide a tool that can validate/fix the block file placement in DataNode data directories Key: HDFS-15303 URL: https://issues.apache.org/jira/browse/HDFS-15303

Changing the default Datanode Volume Choosing policy

Hi, A long time back there was a Jira raised to change the default volume choosing policy from Round Robin to Available Space: https://issues.apache.org/jira/browse/HDFS-8538 At the time there were some objections / concerns about using available space. In the 5 years since then, at Cloudera we

[jira] [Created] (HDFS-15304) Infinite loop between DN and NN at rare condition

Istvan Fajth created HDFS-15304: --- Summary: Infinite loop between DN and NN at rare condition Key: HDFS-15304 URL: https://issues.apache.org/jira/browse/HDFS-15304 Project: Hadoop HDFS Issue Typ

Re: Changing the default Datanode Volume Choosing policy

+1 to switch it on in Hadoop 3.4.0 (1) it doesn't break any existing applications I am aware of. (2) No noticeable performance regression in any cases observed. I feel compelled to make a feature the default if it is strictly better. Hopefully we can make Hadoop easier to use in this way too. On

Re: Changing the default Datanode Volume Choosing policy

I can confirm that my group has run with Available Space for a number of years on the 2.7.x line quite successfully. -Clay From: weic...@cloudera.com.INVALID At: 04/28/20 11:50:27To: sodonn...@cloudera.com.invalid Cc: hdfs-dev@hadoop.apache.org Subject: Re: Changing the default Datanode Volum

[jira] [Created] (HDFS-15305) Extend ViewFS and provide ViewFSOverloadScheme implementation with scheme configurable.

Uma Maheswara Rao G created HDFS-15305: -- Summary: Extend ViewFS and provide ViewFSOverloadScheme implementation with scheme configurable. Key: HDFS-15305 URL: https://issues.apache.org/jira/browse/HDFS-15305

[jira] [Created] (HDFS-15306) Make mount-table to read from central place ( Let's say from HDFS)

Uma Maheswara Rao G created HDFS-15306: -- Summary: Make mount-table to read from central place ( Let's say from HDFS) Key: HDFS-15306 URL: https://issues.apache.org/jira/browse/HDFS-15306 Project:

[jira] [Created] (HDFS-15307) Update description of "dfs.client.socketcache.*" properties to not have mention of short-circuits

Andrey Elenskiy created HDFS-15307: -- Summary: Update description of "dfs.client.socketcache.*" properties to not have mention of short-circuits Key: HDFS-15307 URL: https://issues.apache.org/jira/browse/HDFS-1530

Re: [NOTICE] Removal of protobuf classes from Hadoop Token's public APIs' signature

I'm sorry for coming to this late. I missed this message. It should have been a DISCUSS thread rather than NOTICE. Looks like this is inevitable. But we should make the downstream developers aware & make the update easier. As long as it is stated clearly how to update the code to support Hadoop 3.

[jira] [Resolved] (HDFS-15301) statfs function in hdfs-fuse is not working

[ https://issues.apache.org/jira/browse/HDFS-15301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh resolved HDFS-15301. -- Fix Version/s: 3.4.0 3.3.0 Resolution: Fixed > statfs functio

Re: [NOTICE] Removal of protobuf classes from Hadoop Token's public APIs' signature

hi Wei-Chiu, Can you elaborate on what failures you are facing related to relocated protobuf classes.. ? IFAIK, if the issue with location of protobuf classes, still old jar protobuf-2.5.0.jar will be available in classpath. So downstream depending on 2.5.0 version of protobuf still be able to ac

Re: [NOTICE] Removal of protobuf classes from Hadoop Token's public APIs' signature

Most of the problems are downstream applications using Hadoop's private APIs. Tez: 17:08:38 2020/04/16 00:08:38 INFO: [ERROR] COMPILATION ERROR : 17:08:38 2020/04/16 00:08:38 INFO: [INFO] - 17:08:38 2020/04/16 00:08:38 INFO: