[jira] [Resolved] (HDFS-16946) RBF: top real owners metrics can't been parsed json string

2023-06-12 Thread Ayush Saxena (Jira)


 [ 
https://issues.apache.org/jira/browse/HDFS-16946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ayush Saxena resolved HDFS-16946.
-
Fix Version/s: 3.4.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

> RBF: top real owners metrics can't been parsed json string
> --
>
> Key: HDFS-16946
> URL: https://issues.apache.org/jira/browse/HDFS-16946
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: rbf
>Affects Versions: 3.4.0
>Reporter: Max  Xie
>Assignee: Nishtha Shah
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0
>
> Attachments: image-2023-03-09-22-24-39-833.png
>
>
> After HDFS-15447,  Add top real owners metrics for delegation tokens. But the 
> metrics can't been parsed json string.
>  RBFMetrics$getTopTokenRealOwners method just return 
> `org.apache.hadoop.metrics2.util.Metrics2Util$NameValuePair@1`
> !image-2023-03-09-22-24-39-833.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org



Fwd: [jira] [Created] (HADOOP-18768) Integrating Apache Hadoop into OSS-Fuzz

2023-06-12 Thread Wei-Chiu Chuang
Are there Hadoop committers who would like to help triage bug reports from
OSS-Fuzz?

-- Forwarded message -
From: Henry Lin (Jira) 
Date: Mon, Jun 12, 2023 at 9:10 AM
Subject: [jira] [Created] (HADOOP-18768) Integrating Apache Hadoop into
OSS-Fuzz
To: 


Henry Lin created HADOOP-18768:
--

 Summary: Integrating Apache Hadoop into OSS-Fuzz
 Key: HADOOP-18768
 URL: https://issues.apache.org/jira/browse/HADOOP-18768
 Project: Hadoop Common
  Issue Type: Test
Reporter: Henry Lin


Hi all,

We have prepared the [initial integration|
https://github.com/google/oss-fuzz/pull/10511] of Apache Hadoop into
[Google OSS-Fuzz|https://github.com/google/oss-fuzz] which will provide
more security for your project.



*Why do you need Fuzzing?*
The Code Intelligence JVM fuzzer [Jazzer|
https://github.com/CodeIntelligenceTesting/jazzer] has already found
[hundreds of bugs|
https://github.com/CodeIntelligenceTesting/jazzer/blob/main/docs/findings.md]
in open source projects including for example [OpenJDK|
https://nvd.nist.gov/vuln/detail/CVE-2022-21360], [Protobuf|
https://nvd.nist.gov/vuln/detail/CVE-2021-22569] or [jsoup|
https://github.com/jhy/jsoup/security/advisories/GHSA-m72m-mhq2-9p6c].
Fuzzing proved to be very effective having no false positives. It provides
a crashing input which helps you to reproduce and debug any finding easily.
The integration of your project into the OSS-Fuzz platform will enable
continuous fuzzing of your project by [Jazzer|
https://github.com/CodeIntelligenceTesting/jazzer].



*What do you need to do?*
The integration requires the maintainer or one established project
committer to deal with the bug reports.

You need to create or provide one email address that is associated with a
google account as per [here|
https://google.github.io/oss-fuzz/getting-started/accepting-new-projects/].
When a bug is found, you will receive an email that will provide you with
access to ClusterFuzz, crash reports, code coverage reports and fuzzer
statistics. More than 1 person can be included.



*How can Code Intelligence support you?*
We will continue to add more fuzz targets to improve code coverage over
time. Furthermore, we are permanently enhancing fuzzing technologies by
developing new fuzzers and bug detectors.



Please let me know if you have any questions regarding fuzzing or the
OSS-Fuzz integration.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
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_64

2023-06-12 Thread Apache Jenkins Server
For more details, see 
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/

[Jun 11, 2023, 6:08:13 AM] (github) HADOOP-18718. Fix several maven build 
warnings (#5592). Contributed by Dongjoon Hyun.




-1 overall


The following subsystems voted -1:
blanks hadolint pathlen unit xml


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck


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/resources/xml/external-dtd.xml 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-excerpt.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-missing-tags.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-missing-tags2.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-sample-output.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/fair-scheduler-invalid.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/yarn-site-with-invalid-allocation-file-ref.xml
 

Failed junit tests :

   hadoop.mapreduce.v2.TestUberAM 
   hadoop.mapreduce.v2.TestMRJobsWithProfiler 
   hadoop.mapreduce.v2.TestMRJobs 
  

   cc:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/results-compile-cc-root.txt
 [96K]

   javac:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/results-compile-javac-root.txt
 [12K]

   blanks:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/blanks-eol.txt
 [14M]
  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/blanks-tabs.txt
 [2.0M]

   checkstyle:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/results-checkstyle-root.txt
 [13M]

   hadolint:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/results-hadolint.txt
 [20K]

   pathlen:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/results-pathlen.txt
 [16K]

   pylint:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/results-pylint.txt
 [20K]

   shellcheck:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/results-shellcheck.txt
 [24K]

   xml:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/xml.txt
 [24K]

   javadoc:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/results-javadoc-javadoc-root.txt
 [244K]

   unit:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1255/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-jobclient.txt
 [72K]

Powered by Apache Yetus 0.14.0-SNAPSHOT   https://yetus.apache.org

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-17045) File renamed from a snapshottable dir to a non-snapshottable dir cannot be deleted.

2023-06-12 Thread Tsz-wo Sze (Jira)
Tsz-wo Sze created HDFS-17045:
-

 Summary: File renamed from a snapshottable dir to a 
non-snapshottable dir cannot be deleted.
 Key: HDFS-17045
 URL: https://issues.apache.org/jira/browse/HDFS-17045
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode, snapshots
Reporter: Tsz-wo Sze
Assignee: Tsz-wo Sze






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org