Apache Hadoop qbt Report: branch-2.10+JDK7 on Linux/x86_64

[Apache Jenkins Server]

For more details, see 
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1102/

No changes


ERROR: File 'out/email-report.txt' does not exist

-
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

[Apache Jenkins Server]

For more details, see 
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1301/

[Jul 27, 2023, 3:28:30 AM] (github) HDFS-17117. Print 
reconstructionQueuesInitProgress periodically when BlockManager 
processMisReplicatesAsync. (#5877). Contributed by Haiyang Hu.
[Jul 27, 2023, 7:24:35 AM] (github) YARN-11539. Fix leaf-templates in Flexible 
AQC. (#5868)
[Jul 27, 2023, 7:53:57 AM] (github) HDFS-17120. Support snapshot diff based 
copylisting for flat paths. (#5885)
[Jul 27, 2023, 1:16:34 PM] (github) YARN-11521. Parameterize tests runs with 
legacy/non-legacy queue-mode. (#5883)
[Jul 27, 2023, 3:33:19 PM] (github) YARN-11520. Support capacity vector for 
AQCv2 dynamic templates. (#5871)




-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.hdfs.server.namenode.ha.TestObserverNode 
   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/1301/artifact/out/results-compile-cc-root.txt
 [96K]

   javac:

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

   blanks:

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

   checkstyle:

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

   hadolint:

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

   pathlen:

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

   pylint:

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

   shellcheck:

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

   xml:

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

   javadoc:

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

   unit:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1301/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
 [236K]
  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1301/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: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: HADOOP-18207 hadoop-logging module about to land

[Ayush Saxena]

Started from the bottom, a lot of irrelevant information,
java,jersey,eclipse, finally I gave up, bit of emotional stuff also,
so didn’t read the whole mail itself.

Quoting:
///->
>
hurts a bit is the fact that despite the whole discussion that took place
on the parent Jira, and the clear agreements/directions we have agreed
upon, we are still engaging in the discussion to determine the value this
work brings in.
<-///

Final derrivatives: a lot of discussion happened on the ticket itself,
patch is ready since 4 months(slow reveiewer to blame?), but few weeks
because of me, just for folks, because the ‘extensive‘ review didn’t
involves running the failed or checking even the jenkins result & it
broke obviously and then directly coming & merging based on a non
binding vote. No worries, Who cares!!!

So, I am late into the party & on the wrong venue and not an 'expert'
so not in the guest list either, *Typical ‘Not Open To
Discussion/Feedback’ scenario*, moving forward here in such a scenario
is getting into arguments & finally a fight, which I am pretty sure
atleast neither I nor Wei-Chiu is interested in. One day increased
also today, Next time make sure Wei-Chiu it is 15mins otherwise we
loose scope to say anything & people get hurt also :-)

So, my opinion/vote doesn’t hold here atleast, so didn't bother to
read also, go ahead folks. Next time I will be on time and the right
place. Please refrain from putting mails like these on dev lists after
months, can directly merge!!!

PS. IA & IS is something we hardly update now and hardly mark anything
on the higher side and we use mostly to get away with ‘unavoidable’
circumstances, not to dodge everything, functional compat is very
important irrespective of anything and just a behaviour change is not
"just" a behaviour change & is sometimes the reason for folks not
upgrading!!! Talk to folks and projects still on 2.x

PPS. There are too many experts... The ‘Hadoop’ Experts who already
said  the final yes already. Curious: who all clasify as one, do we
have a list of them? Just kidding I know that!!!, just for fact who so
ever tells people he is the Hadoop expert, ok, but he is not Hadoop &
Hadoop is not only him.

Passed fedback already & I am done, It is good enough for the
'experts' to decode. Will abstain from commenting or following mail
thread further. Last 2 cents, should not encourage these 90/95%
things, leaves technical debts for others to clean up, if the guy
doesn't comes back for the remaining, in general which is the usual
case.

Sigh...

-Ayush

> On 28-Jul-2023, at 2:25 AM, Viraj Jasani  wrote:
>
> Thank you Wei-Chiu for the thread and extensive help with reviews! Thank
> you Ayush for responding to the thread!
> Let me try to address some points.
>
> Please pardon my ignorance if I am not supposed to respond to any of the
> questions.
>
>> Regarding this entire activity including the parent tickets: Do we have
> any dev list agreement for this?
>
> HADOOP-16206  was
> created back in Mar, 2019 and there has been tons of discussion on the Jira
> since then. Duo is an expert and he has also worked with our esteemed Log4j
> community to introduce changes that promise great benefits for both hbase
> and hadoop projects (for instance, [1]). He has laid out the plan to tackle
> the whole migration, one small piece at a time and there has been enough
> agreement on the Jira from Hadoop experts, some of Log4j community members
> also chimed in and provided their feedbacks, and it has been agreed upon to
> proceed with Duo's proposed plan and integrate the changes into the trunk.
> This will enable us to stabilize the work gradually over time.
> The Jira has received many interactions over the past few years.
>
>
>> What incompatibilities have been introduced till now for this and what
> are planned.
>
> Let me list down what has been done so far, that might be easier to discuss:
>
>
> - HADOOP-18206  removed
> commons-logging references, the project is no longer under any active
> development cycle (last release on 2014
> https://github.com/apache/commons-logging/tags), and without this
> cleanup, it becomes very difficult to chase log4j changes. No direct
> incompatibility involved.
> - HADOOP-18653 
> follow-up
> to ensure we use slf4j log4j adaptor to ensure slf4j is in the classpath
> before we update loglevel (dynamically change log level using servlet). No
> incompatibility introduced.
> - HADOOP-18648  kms
> log4j properties should not be loaded dynamically as this is no longer
> supported by log4j2, instead use HADOOP_OPTS to provide log4j properties
> location. No incompatibility introduced.
> - HADOOP-18654 
> TaskLogAppender
> is not being used, remove it. It was marked IA.Private and