Re: [DISCUSS] what needs to be done to switch to java17

[Ashutosh Gupta]

Thanks, everyone, for starting this discussion. This sounds like a good
plan to start with. As I was working on the JUnit 4 to 5 upgrade, I paused
for a while as I got occupied with other stuff. But I would be happy to
complete it as part of the Java switch process.

On Tue, Jul 30, 2024 at 4:21 AM slfan1989  wrote:

> Thank you very much for initiating this discussion! I am also very much
> looking forward to JDK 17. I have observed that using --add-opens= is quite
> common in other Apache projects. One thing I know is that it is necessary
> to upgrade JUnit 4 to JUnit 5. There are some JIRA issues currently being
> worked on for this. For YARN MapReduce, some pull requests have already
> been completed for this feature. Upgrading Jersey is a very challenging
> project. Currently, our upgrade strategy is to perform it all at once. If
> we can find a way to break Jersey down into individual modules for
> upgrading, it might be much easier.
>
> I have successfully debugged most of the unit tests for YARN's
> ResourceManager and NodeManager.(Upgrade Jersey 2.4.1)  Additionally, we
> are using Hadoop compiled with JDK 17 internally (mainly on the current
> trunk branch with --add-opens=). We have replaced over 600 NM instances,
> and this part is functioning normally. Therefore, I believe we are
> essentially ready to upgrade to JDK 17.
>
> My idea is to create a separate branch specifically for upgrading to JDK
> 17. After debugging and ensuring everything works, we can then merge this
> branch into the trunk branch.
>
> By the way, there's a JIRA that we have had to revert twice
> (HADOOP-19071)[1], which involves upgrading the maven-surefire-plugin.
>
> [1] https://issues.apache.org/jira/browse/HADOOP-19071
>
> - Shilun Fan
>
> On Tue, 30 Jul 2024 at 06:37, Shilun Fan wrote:
>
> > Depends on what we mean by switching to JDK-17, Compile time support
> > or Runtime support, We don't have compile time support for JDK-11 too,
> > it is just runtime, We have a daily build as well for JDK-11, which
> > has now some genuine failures now, need to check [1], as of now the
> > version is hardcoded here [2], unless we change here it but just
> > change our local JAVA_HOME, it will compile with JDK-17 as well I
> > believe
>
> > So, If we are to chase the runtime support we can setup a regular CI
> > with JDK-17 like we have one for JDK-11, there were some test failures
> > reported as part of HADOOP-18716, most of them should be fixable by
> > some dependency upgrades or some hacks like adding one of these
> > ```
> > --add-opens=java.base/java.net=ALL-UNNAMED
> > --add-opens=java.base/java.util=ALL-UNNAMED
> > --add-opens=java.base/java.util.concurrent=ALL-UNNAMED
> > --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED
> > --add-opens=java.base/java.lang=ALL-UNNAMED
> > --add-opens=java.base/java.util.regex=ALL-UNNAMED
> > --add-opens=java.base/java.io=ALL-UNNAMED
> > ```
>
> > That is some typical JDK-17 hack
>
> > For the compile support, that is we change the value at [2] to 17, I
> > think then some bigger problems will surface, One I know is Jersey
> > creates some issues for sure, We need to upgrade Jersey, As per this
> > [3] to Jersey 2.35+ or do some hack to use a patched jersey version
> > with minimal change which can unblock the JDK-17 initiative
>
> > -Ayush
>
>
> > [1]
> https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/709/
> > [2]
>
> https://github.com/apache/hadoop/blob/038636a1b5250e06622cac7ee11b12965c9e/hadoop-project/pom.xml#L160
> > [3] https://github.com/eclipse-ee4j/jersey/wiki/Road-Map
>
> On Tue, 30 Jul 2024 at 00:53, PJ Fanning wrote:
> >
> > I think this is worth considering. I think it would require a minor
> > release like 3.5.0 as opposed to considering it for future 3.4.x patch
> > releases.
> > I tend to build locally with Java 11, by default and I haven't hit
> > major issues building Hadoop. There may be some gotcha somewhere but
> > it is likely to be easy enough to fix.
> >
> > It's probably only a matter of time before some important dependency
> > jars for Hadoop require Java 11 or 17.
> >
> > On Mon, 29 Jul 2024 at 20:04, Steve Loughran
> > wrote:
> > >
> > > A lot of projects are moving off java8. making java17 the new baseline
> > >
> > > what do we need to there that is blocker rather than just "nice"'?
> >
> > -
> > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
> >
>
> -
> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
>

Re: [VOTE] Release Apache Hadoop 3.3.6 RC0

[Ashutosh Gupta]

Hi

Thanks Wei-Chiu for driving the release.

+1 (non-binding)

* Builds from source looks good.
* Checksums and signatures look good.
* Running basic HDFS commands and running simple MapReduce jobs looks good.
* hadoop-tools/hadoop-aws UTs and ITs looks good

Thanks,
Ash

On Tue, Jun 20, 2023 at 5:18 PM Mukund Madhav Thakur
 wrote:

> Hi Wei-Chiu,
> Thanks for driving the release.
>
> +1 (binding)
> Verified checksum and signature.
> Built from source successfully.
> Ran aws Itests
> Ran azure Itests
> Compiled hadoop-api-shim
> Compiled google cloud storage.
>
>
> I did see the two test failures in GCS connector as well but those are
> harmless.
>
>
>
> On Thu, Jun 15, 2023 at 8:21 PM Wei-Chiu Chuang
>  wrote:
>
> > Overall so far so good.
> >
> > hadoop-api-shim:
> > built, tested successfully.
> >
> > cloudstore:
> > built successfully.
> >
> > Spark:
> > built successfully. Passed hadoop-cloud tests.
> >
> > Ozone:
> > One test failure due to unrelated Ozone issue. This test is being
> disabled
> > in the latest Ozone code.
> >
> > org.apache.hadoop.hdds.utils.NativeLibraryNotLoadedException: Unable
> > to load library ozone_rocksdb_tools from both java.library.path &
> > resource file libozone_rocksdb_t
> > ools.so from jar.
> > at
> >
> org.apache.hadoop.hdds.utils.db.managed.ManagedSSTDumpTool.(ManagedSSTDumpTool.java:49)
> >
> >
> > Google gcs:
> > There are two test failures. The tests were added recently by
> HADOOP-18724
> >  in Hadoop 3.3.6.
> This
> > is okay. Not production code problem. Can be addressed in GCS code.
> >
> > [ERROR] Errors:
> > [ERROR]
> >
> >
> TestInMemoryGoogleContractOpen>AbstractContractOpenTest.testFloatingPointLength:403
> > » IllegalArgument Unknown mandatory key for gs://fake-in-memory-test-buck
> > et/contract-test/testFloatingPointLength "fs.option.openfile.length"
> > [ERROR]
> >
> >
> TestInMemoryGoogleContractOpen>AbstractContractOpenTest.testOpenFileApplyAsyncRead:341
> > » IllegalArgument Unknown mandatory key for gs://fake-in-memory-test-b
> > ucket/contract-test/testOpenFileApplyAsyncRead
> "fs.option.openfile.length"
> >
> >
> >
> >
> >
> > On Wed, Jun 14, 2023 at 5:01 PM Wei-Chiu Chuang 
> > wrote:
> >
> > > The hbase-filesystem tests passed after reverting HADOOP-18596
> > >  and HADOOP-18633
> > >  from my local
> tree.
> > > So I think it's a matter of the default behavior being changed. It's
> not
> > > the end of the world. I think we can address it by adding an
> incompatible
> > > change flag and a release note.
> > >
> > > On Wed, Jun 14, 2023 at 3:55 PM Wei-Chiu Chuang 
> > > wrote:
> > >
> > >> Cross referenced git history and jira. Changelog needs some update
> > >>
> > >> Not in the release
> > >>
> > >>1. HDFS-16858 
> > >>
> > >>
> > >>1. HADOOP-18532 <
> https://issues.apache.org/jira/browse/HADOOP-18532>
> > >>2.
> > >>   1. HDFS-16861  >
> > >>  2.
> > >> 1. HDFS-16866
> > >> 
> > >> 2.
> > >>1. HADOOP-18320
> > >>
> > >>2.
> > >>
> > >> Updated fixed version. Will generate. new Changelog in the next RC.
> > >>
> > >> Was able to build HBase and hbase-filesystem without any code change.
> > >>
> > >> hbase has one unit test failure. This one is reproducible even with
> > >> Hadoop 3.3.5, so maybe a red herring. Local env or something.
> > >>
> > >> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed:
> > >> 9.007 s <<< FAILURE! - in
> > >> org.apache.hadoop.hbase.regionserver.TestSyncTimeRangeTracker
> > >> [ERROR]
> > >>
> >
> org.apache.hadoop.hbase.regionserver.TestSyncTimeRangeTracker.testConcurrentIncludeTimestampCorrectness
> > >>  Time elapsed: 3.13 s  <<< ERROR!
> > >> java.lang.OutOfMemoryError: Java heap space
> > >> at
> > >>
> >
> org.apache.hadoop.hbase.regionserver.TestSyncTimeRangeTracker$RandomTestData.(TestSyncTimeRangeTracker.java:91)
> > >> at
> > >>
> >
> org.apache.hadoop.hbase.regionserver.TestSyncTimeRangeTracker.testConcurrentIncludeTimestampCorrectness(TestSyncTimeRangeTracker.java:156)
> > >>
> > >> hbase-filesystem has three test failures in TestHBOSSContractDistCp,
> and
> > >> is not reproducible with Hadoop 3.3.5.
> > >> [ERROR] Failures: [ERROR]
> > >>
> >
> TestHBOSSContractDistCp>AbstractContractDistCpTest.testDistCpUpdateCheckFileSkip:976->Assert.fail:88
> > >> 10 errors in file of length 10
> > >> [ERROR]
> > >>
> >
> TestHBOSSContractDistCp>AbstractContractDistCpTest.testUpdateDeepDirectoryStructureNoChange:270->AbstractContractDistCpTest.assertCounterInRange:290->Assert.assertTrue:41->Assert.fail:88
> > >> Files Ski

Re: [VOTE] Release Apache Hadoop 3.3.5 (RC3)

[Ashutosh Gupta]

Hi Steve

I will also do it by today/tomorrow.

Thanks,
Ashutosh

On Sat, 18 Mar, 2023, 4:07 pm Steve Loughran, 
wrote:

> Thank you for this!
>
> Can anyone else with time do a review too? i really want to get this one
> done, now the HDFS issues are all resolved.
>
> I do not want this release to fall by the wayside through lack of votes
> alone. In fact, I would be very unhappy
>
>
>
> On Sat, 18 Mar 2023 at 06:47, Viraj Jasani  wrote:
>
> > +1 (non-binding)
> >
> > * Signature/Checksum: ok
> > * Rat check (1.8.0_341): ok
> >  - mvn clean apache-rat:check
> > * Built from source (1.8.0_341): ok
> >  - mvn clean install  -DskipTests
> > * Built tar from source (1.8.0_341): ok
> >  - mvn clean package  -Pdist -DskipTests -Dtar -Dmaven.javadoc.skip=true
> >
> > Containerized deployments:
> > * Deployed and started Hdfs - NN, DN, JN with Hbase 2.5 and Zookeeper 3.7
> > * Deployed and started JHS, RM, NM
> > * Hbase, hdfs CRUD looks good
> > * Sample RowCount MapReduce job looks good
> >
> > * S3A tests with scale profile looks good
> >
> >
> > On Wed, Mar 15, 2023 at 12:48 PM Steve Loughran
> > 
> > wrote:
> >
> > > Apache Hadoop 3.3.5
> > >
> > > Mukund and I have put together a release candidate (RC3) for Hadoop
> > 3.3.5.
> > >
> > > What we would like is for anyone who can to verify the tarballs,
> > especially
> > > anyone who can try the arm64 binaries as we want to include them too.
> > >
> > > The RC is available at:
> > > https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.5-RC3/
> > >
> > > The git tag is release-3.3.5-RC3, commit 706d88266ab
> > >
> > > The maven artifacts are staged at
> > >
> https://repository.apache.org/content/repositories/orgapachehadoop-1369/
> > >
> > > You can find my public key at:
> > > https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> > >
> > > Change log
> > >
> >
> https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.5-RC3/CHANGELOG.md
> > >
> > > Release notes
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.5-RC3/RELEASENOTES.md
> > >
> > > This is off branch-3.3 and is the first big release since 3.3.2.
> > >
> > > Key changes include
> > >
> > > * Big update of dependencies to try and keep those reports of
> > >   transitive CVEs under control -both genuine and false positives.
> > > * HDFS RBF enhancements
> > > * Critical fix to ABFS input stream prefetching for correct reading.
> > > * Vectored IO API for all FSDataInputStream implementations, with
> > >   high-performance versions for file:// and s3a:// filesystems.
> > >   file:// through java native io
> > >   s3a:// parallel GET requests.
> > > * This release includes Arm64 binaries. Please can anyone with
> > >   compatible systems validate these.
> > > * and compared to the previous RC, all the major changes are
> > >   HDFS issues.
> > >
> > > Note, because the arm64 binaries are built separately on a different
> > > platform and JVM, their jar files may not match those of the x86
> > > release -and therefore the maven artifacts. I don't think this is
> > > an issue (the ASF actually releases source tarballs, the binaries are
> > > there for help only, though with the maven repo that's a bit blurred).
> > >
> > > The only way to be consistent would actually untar the x86.tar.gz,
> > > overwrite its binaries with the arm stuff, retar, sign and push out
> > > for the vote. Even automating that would be risky.
> > >
> > > Please try the release and vote. The vote will run for 5 days.
> > >
> > > -Steve
> > >
> >
>

Re: [ANNOUNCE] New Hadoop PMC member - Mukund Thakur

[Ashutosh Gupta]

Congratulations Mukund. Well deserved!

On Wed, 8 Feb, 2023, 11:07 pm Mukund Madhav Thakur,
 wrote:

> Thanks Everyone :)
>
> On Wed, Feb 8, 2023 at 4:28 PM Sunil Govindan  wrote:
>
> > Congratulations Mukund!!!
> >
> > Thanks
> > Sunil
> >
> > On Wed, Feb 8, 2023 at 1:48 AM Vinayakumar B 
> > wrote:
> >
> > > On behalf of the Apache Hadoop PMC, I am pleased to announce that
> Mukund
> > > Thakur (mthakur) has accepted the PMC's invitation to become a PMC
> member
> > > on
> > > the project. We appreciate all of Mukund’s generous contributions thus
> > far
> > > and look forward to his continued involvement.
> > >
> > > Congratulations and welcome, Mukund !
> > >
> > > -Vinayakumar B
> > > --
> > > -Vinay
> > >
> >
>

Re: MapReduce Terasort job is slow on Java 11

[Ashutosh Gupta]

Hi Wei-Chiu

We are running all the processes on JDK11 and not just the MR job.

Thanks,
Ashutosh

On Wed, Nov 23, 2022 at 4:59 PM Wei-Chiu Chuang  wrote:

> For the JDK11 case, does everyone on the cluster run on JDK11? or is it the
> MR job that is on JDK11?
>
> We have users running JDK in production. The NN GC performance was the only
> thing we were aware of.
> In the past we noticed because JDK11 uses G1GC by default, large NameNode
> performance was worse than JDK8 which uses CMS.
>
>
> On Wed, Nov 23, 2022 at 8:44 AM Prabhu Joseph 
> wrote:
>
> > Hi, Any pointers on why the MapReduce Terasort job is slower on Java 11
> > compared with Java 8. Input data, Configs, Number of Worker Nodes, Node
> > instance type, Hadoop version and Resources are the same in both the
> runs.
> > Have compared App logs of both good and bad runs and observed Avg Task
> > (both Map and Reduce) time is slower in Java 11.
> >
> > *Java 8 : **7 min 2 secs *
> >
> > hadoop jar /usr/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar
> terasort
> > -Dmapred.reduce.tasks=120
> > /tmp/terasort/127130b1-ceb0-422c-a957-48c651b20f30/input/
> > /tmp/terasort/127130b1-ceb0-422c-a957-48c651b20f30/output/
> > 2022-11-23 12:22:41,948 INFO terasort.TeraSort: starting
> > 2022-11-23 12:29:59,520 INFO terasort.TeraSort: done
> >
> > *Java 11 : 9 min 37 secs *
> >
> > [hadoop@ip-172-31-60-208 ~]$ hadoop jar
> > /usr/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar terasort
> > -Dmapred.reduce.tasks=120
> > /tmp/terasort/127130b1-ceb0-422c-a957-48c651b20f30/input/
> > /tmp/terasort/127130b1-ceb0-422c-a957-48c651b20f30/output/
> > 2022-11-23 12:22:44,167 INFO terasort.TeraSort: starting
> > 2022-11-23 12:32:21,791 INFO terasort.TeraSort: done
> >
> > Thanks,
> > Prabhu Joseph
> >
>

Re: MapReduce Terasort job is slow on Java 11

[Ashutosh Gupta]

Hi Prabhu

Thanks for bringing this to attention. I can see it as part of this JIRA -
HADOOP-15338 . It was
also pointed out in the past as well about the degradation by @Ayush and
@zhenhe. We should continue this discussion.

@Ayush, did we get to know the root cause by any chance?

Thanks & Regards,
Ashutosh

On Wed, Nov 23, 2022 at 4:44 PM Prabhu Joseph 
wrote:

> Hi, Any pointers on why the MapReduce Terasort job is slower on Java 11
> compared with Java 8. Input data, Configs, Number of Worker Nodes, Node
> instance type, Hadoop version and Resources are the same in both the runs.
> Have compared App logs of both good and bad runs and observed Avg Task
> (both Map and Reduce) time is slower in Java 11.
>
> *Java 8 : **7 min 2 secs *
>
> hadoop jar /usr/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar terasort
> -Dmapred.reduce.tasks=120
> /tmp/terasort/127130b1-ceb0-422c-a957-48c651b20f30/input/
> /tmp/terasort/127130b1-ceb0-422c-a957-48c651b20f30/output/
> 2022-11-23 12:22:41,948 INFO terasort.TeraSort: starting
> 2022-11-23 12:29:59,520 INFO terasort.TeraSort: done
>
> *Java 11 : 9 min 37 secs *
>
> [hadoop@ip-172-31-60-208 ~]$ hadoop jar
> /usr/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar terasort
> -Dmapred.reduce.tasks=120
> /tmp/terasort/127130b1-ceb0-422c-a957-48c651b20f30/input/
> /tmp/terasort/127130b1-ceb0-422c-a957-48c651b20f30/output/
> 2022-11-23 12:22:44,167 INFO terasort.TeraSort: starting
> 2022-11-23 12:32:21,791 INFO terasort.TeraSort: done
>
> Thanks,
> Prabhu Joseph
>

[jira] [Created] (YARN-11364) Docker to accept Image name with sha256

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11364:
-

 Summary: Docker to accept Image name with sha256
 Key: YARN-11364
 URL: https://issues.apache.org/jira/browse/YARN-11364
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: yarn
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta


While using docker and passing the sha 256 of the image as an image uri. The 
sha256 is not getting picked up and emr throws invalid image uri



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

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

[jira] [Created] (YARN-11363) Remove unused TimelineVersionWatcher and TimelineVersion from hadoop-yarn-server-tests

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11363:
-

 Summary: Remove unused TimelineVersionWatcher and TimelineVersion 
from hadoop-yarn-server-tests 
 Key: YARN-11363
 URL: https://issues.apache.org/jira/browse/YARN-11363
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: test, yarn
Affects Versions: 3.3.4, 3.3.3
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta


Verify and remove unused TimelineVersionWatcher and TimelineVersion from 
hadoop-yarn-server-tests 



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

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

[jira] [Resolved] (YARN-11259) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice

[Ashutosh Gupta (Jira)]

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

Ashutosh Gupta resolved YARN-11259.
---
Resolution: Duplicate

> Upgrade JUnit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
> -
>
> Key: YARN-11259
> URL: https://issues.apache.org/jira/browse/YARN-11259
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: yarn
>Affects Versions: 3.3.4
>    Reporter: Ashutosh Gupta
>    Assignee: Ashutosh Gupta
>Priority: Major
>




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

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

[jira] [Created] (YARN-11339) Upgrade Junit 4 to 5 in hadoop-yarn-services-api

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11339:
-

 Summary: Upgrade Junit 4 to 5 in hadoop-yarn-services-api
 Key: YARN-11339
 URL: https://issues.apache.org/jira/browse/YARN-11339
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: test
Affects Versions: 3.3.4, 3.3.3
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta


Upgrade Junit 4 to 5 in hadoop-yarn-services-api



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

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

[jira] [Created] (YARN-11338) Upgrade Junit 4 to 5 in hadoop-yarn-applications-unmanaged-am-launcher

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11338:
-

 Summary: Upgrade Junit 4 to 5 in 
hadoop-yarn-applications-unmanaged-am-launcher
 Key: YARN-11338
 URL: https://issues.apache.org/jira/browse/YARN-11338
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: test
Affects Versions: 3.3.4
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta


Upgrade Junit 4 to 5 in hadoop-yarn-applications-unmanaged-am-launcher



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

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

[jira] [Created] (YARN-11337) Upgrade Junit 4 to 5 in hadoop-yarn-applications-mawo

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11337:
-

 Summary: Upgrade Junit 4 to 5 in hadoop-yarn-applications-mawo
 Key: YARN-11337
 URL: https://issues.apache.org/jira/browse/YARN-11337
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: test
Affects Versions: 3.3.4, 3.3.3
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta
 Fix For: 3.4.0


Upgrade Junit 4 to 5 in hadoop-yarn-applications-mawo



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

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

[jira] [Created] (YARN-11336) Upgrade Junit 4 to 5 in hadoop-yarn-applications-catalog-webapp

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11336:
-

 Summary: Upgrade Junit 4 to 5 in 
hadoop-yarn-applications-catalog-webapp
 Key: YARN-11336
 URL: https://issues.apache.org/jira/browse/YARN-11336
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: test
Affects Versions: 3.3.4, 3.3.3
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta


Upgrade Junit 4 to 5 in hadoop-yarn-applications-catalog-webapp



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

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

Re: [VOTE] Release Apache Hadoop 3.3.4

[Ashutosh Gupta]

+1 (non-binding)

* Builds from source looks good.
* Checksums and signatures are correct.
* Running basic HDFS commands and running simple MapReduce jobs looks good.
* Skimmed through the contents of site documentation and it looks good.

Thanks Steve for driving this release.

Ashutosh


On Wed, Aug 3, 2022 at 9:39 PM Chris Nauroth  wrote:

> +1 (binding)
>
> * Verified all checksums.
> * Verified all signatures.
> * Built from source, including native code on Linux.
> * mvn clean package -Pnative -Psrc -Drequire.openssl -Drequire.snappy
> -Drequire.zstd -DskipTests
> * Tests passed.
> * mvn --fail-never clean test -Pnative -Dparallel-tests
> -Drequire.snappy -Drequire.zstd -Drequire.openssl
> -Dsurefire.rerunFailingTestsCount=3 -DtestsThreadCount=8
> * Checked dependency tree to make sure we have all of the expected library
> updates that are mentioned in the release notes.
> * mvn -o dependency:tree
>
> I saw a LibHDFS test failure, but I know it's something flaky that's
> already tracked in a JIRA issue. The release looks good. Steve, thank you
> for driving this.
>
> Chris Nauroth
>
>
> On Wed, Aug 3, 2022 at 11:27 AM Steve Loughran  >
> wrote:
>
> > my vote for this is +1, binding.
> >
> > obviously I`m biased, but i do not want to have to issue any more interim
> > releases before the feature release off branch-3.3, so I am trying to be
> > ruthless.
> >
> > my client vaidator ant project has a more targets to help with releasing,
> > and now builds a lot mor of my local projects
> > https://github.com/steveloughran/validate-hadoop-client-artifacts
> > all good as far as my test coverage goes, with these projects validating
> > the staged dependencies.
> >
> > now, who else can review
> >
> > On Fri, 29 Jul 2022 at 19:47, Steve Loughran 
> wrote:
> >
> > >
> > >
> > > I have put together a release candidate (RC1) for Hadoop 3.3.4
> > >
> > > The RC is available at:
> > > https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.4-RC1/
> > >
> > > The git tag is release-3.3.4-RC1, commit a585a73c3e0
> > >
> > > The maven artifacts are staged at
> > >
> https://repository.apache.org/content/repositories/orgapachehadoop-1358/
> > >
> > > You can find my public key at:
> > > https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> > >
> > > Change log
> > >
> >
> https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.4-RC1/CHANGELOG.md
> > >
> > > Release notes
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.4-RC1/RELEASENOTES.md
> > >
> > > There's a very small number of changes, primarily critical
> code/packaging
> > > issues and security fixes.
> > >
> > > See the release notes for details.
> > >
> > > Please try the release and vote. The vote will run for 5 days.
> > >
> > > steve
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 3.2.4 - RC0

[Ashutosh Gupta]

+1(non-binding)

* Builds from source look good.
* Checksums and signatures are correct.
* Running basic HDFS and MapReduce commands looks good.

> * TestAMRMProxy - Not able to reproduce in local
> * TestFsck - I can see failure only I can see is
 TestFsck.testFsckListCorruptSnapshotFiles which passed after applying
HDFS-15038
> * TestSLSStreamAMSynth - Not able to reproduce in local
> * TestServiceAM - Not able to reproduce in local

Thanks Masatake for driving this release.

On Thu, Jul 21, 2022 at 5:51 AM Masatake Iwasaki 
wrote:

> Hi developers,
>
> I'm still waiting for your vote.
> I'm considering the intermittent test failures mentioned by Chris are not
> blocker.
> Please file a JIRA and let me know if you find a blocker issue.
>
> I will appreciate your help for the release process.
>
> Regards,
> Masatake Iwasaki
>
> On 2022/07/20 14:50, Masatake Iwasaki wrote:
> >> TestServiceAM
> >
> > I can see the reported failure of TestServiceAM in some "Apache Hadoop
> qbt Report: branch-3.2+JDK8 on Linux/x86_64".
> > 3.3.0 and above might be fixed by YARN-8867 which added guard using
> GenericTestUtils#waitFor for stabilizing the
> testContainersReleasedWhenPreLaunchFails.
> > YARN 8867 did not modified other code under hadoop-yarn-services.
> > If it is the case, TestServiceAM can be tagged as flaky in branch-3.2.
> >
> >
> > On 2022/07/20 14:21, Masatake Iwasaki wrote:
> >> Thanks for testing the RC0, Chris.
> >>
> >>> The following are new test failures for me on 3.2.4:
> >>> * TestAMRMProxy
> >>> * TestFsck
> >>> * TestSLSStreamAMSynth
> >>> * TestServiceAM
> >>
> >> I could not reproduce the test failures on my local.
> >>
> >> For TestFsck, if the failed test case is
> testFsckListCorruptSnapshotFiles,
> >> cherry-picking HDFS-15038 (fixing only test code) could be the fix.
> >>
> >> The failure of TestSLSStreamAMSynth looks frequently reported by
> >> "Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86_64".
> >> It could be tagged as known flaky test.
> >>
> >> On 2022/07/20 9:15, Chris Nauroth wrote:
> >>> -0 (binding)
> >>>
> >>> * Verified all checksums.
> >>> * Verified all signatures.
> >>> * Built from source, including native code on Linux.
> >>>  * mvn clean package -Pnative -Psrc -Drequire.openssl
> -Drequire.snappy
> >>> -Drequire.zstd -DskipTests
> >>> * Tests mostly passed, but see below.
> >>>  * mvn --fail-never clean test -Pnative -Dparallel-tests
> >>> -Drequire.snappy -Drequire.zstd -Drequire.openssl
> >>> -Dsurefire.rerunFailingTestsCount=3 -DtestsThreadCount=8
> >>>
> >>> The following are new test failures for me on 3.2.4:
> >>> * TestAMRMProxy
> >>> * TestFsck
> >>> * TestSLSStreamAMSynth
> >>> * TestServiceAM
> >>>
> >>> The following tests also failed, but they also fail for me on 3.2.3, so
> >>> they aren't likely to be related to this release candidate:
> >>> * TestCapacitySchedulerNodeLabelUpdate
> >>> * TestFrameworkUploader
> >>> * TestSLSGenericSynth
> >>> * TestSLSRunner
> >>> * test_libhdfs_threaded_hdfspp_test_shim_static
> >>>
> >>> I'm not voting a full -1, because I haven't done any root cause
> analysis on
> >>> these new test failures. I don't know if it's a quirk to my
> environment,
> >>> though I'm using the start-build-env.sh Docker container, so any build
> >>> dependencies should be consistent. I'd be comfortable moving ahead if
> >>> others are seeing these tests pass.
> >>>
> >>> Chris Nauroth
> >>>
> >>>
> >>> On Thu, Jul 14, 2022 at 7:57 AM Masatake Iwasaki <
> iwasak...@oss.nttdata.com>
> >>> wrote:
> >>>
>  +1 from myself.
> 
>  * skimmed the contents of site documentation.
> 
>  * built the source tarball on Rocky Linux 8 (x86_64) by OpenJDK 8 with
>  `-Pnative`.
> 
>  * launched pseudo distributed cluster including kms and httpfs with
>  Kerberos and SSL enabled.
> 
>  * created encryption zone, put and read files via httpfs.
>  * ran example MR wordcount over encryption zone.
> 
>  * launched 3-node docker cluster with NN-HA and RM-HA enabled and ran
> some
>  example MR jobs.
> 
>  * built HBase 2.4.11, Hive 3.1.2 and Spark 3.1.2 against Hadoop 3.2.4
> RC0
>  on CentOS 7 (x86_64) by using Bigtop branch-3.1 and ran
> smoke-tests.
>  https://github.com/apache/bigtop/pull/942
> 
>  * Hive needs updating exclusion rule to address HADOOP-18088
> (migration
>  to reload4j).
> 
>  * built Spark 3.3.0 against Hadoop 3.2.4 RC0 using the staging
> repository::
> 
>    
>   staged
>   staged-releases
>   
> 
> https://repository.apache.org/content/repositories/orgapachehadoop-1354
>  
>   
> true
>   
>   
> true
>   
> 
> 
>  Thanks,
>  Masatake Iwasaki
> 
>  On 2022/07/13 1:14, Masatake Iwasaki wrote:
> > Hi all,
> >
> > Here's Hadoop 3.2.4 release candida

[jira] [Resolved] (YARN-10121) In Federation executing yarn queue status command throws an exception

[Ashutosh Gupta (Jira)]

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

Ashutosh Gupta resolved YARN-10121.
---
Resolution: Not A Problem

> In Federation executing yarn queue status command throws an exception
> -
>
> Key: YARN-10121
> URL: https://issues.apache.org/jira/browse/YARN-10121
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: federation, yarn
>Reporter: Sushanta Sen
>Assignee: fanshilun
>Priority: Major
> Fix For: 3.4.0
>
>
> yarn queue status is failing, prompting an error 
> “org.apache.commons.lang.NotImplementedException: Code is not implemented”.
> {noformat}
>  ./yarn queue -status default
> Exception in thread "main" org.apache.commons.lang.NotImplementedException: 
> Code is not implemented
> at 
> org.apache.hadoop.yarn.server.router.clientrm.FederationClientInterceptor.getQueueInfo(FederationClientInterceptor.java:715)
> at 
> org.apache.hadoop.yarn.server.router.clientrm.RouterClientRMService.getQueueInfo(RouterClientRMService.java:246)
> at 
> org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.getQueueInfo(ApplicationClientProtocolPBServiceImpl.java:328)
> at 
> org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:591)
> at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:530)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1036)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:928)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:863)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1729)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2793)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at 
> org.apache.hadoop.yarn.ipc.RPCUtil.instantiateException(RPCUtil.java:53)
> at 
> org.apache.hadoop.yarn.ipc.RPCUtil.instantiateRuntimeException(RPCUtil.java:85)
> at 
> org.apache.hadoop.yarn.ipc.RPCUtil.unwrapAndThrowException(RPCUtil.java:122)
> at 
> org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getQueueInfo(ApplicationClientProtocolPBClientImpl.java:341)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
> at 
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
> at 
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
> at 
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
> at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
> at com.sun.proxy.$Proxy8.getQueueInfo(Unknown Source)
> at 
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.getQueueInfo(YarnClientImpl.java:650)
> at 
> org.apache.hadoop.yarn.client.cli.QueueCLI.listQueue(QueueCLI.java:111)
> at org.apache.hadoop.yarn.client.cli.QueueCLI.run(QueueCLI.java:78)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> at org.apache.hadoop.yarn.client.cli.QueueCLI.main(QueueCLI.java:50)
> {noformat}



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

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

[jira] [Created] (YARN-11197) Backport YARN 9608 DecommissioningNodesWatcher should get lists of running applications on node from RMNode.

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11197:
-

 Summary: Backport YARN 9608 DecommissioningNodesWatcher should get 
lists of running applications on node from RMNode.
 Key: YARN-11197
 URL: https://issues.apache.org/jira/browse/YARN-11197
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: resourcemanager
Affects Versions: 2.10.2, 2.10.1
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta


There has been ask in community and internally as well to have YARN-9608 for 
hadoop-2.10 as well. 

Evaluate and creating patch for the same. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Re: [VOTE] Release Apache Hadoop 2.10.2 - RC0

[Ashutosh Gupta]

+1(non-binding)

* Builds from source look good.
* Checksums and signatures are correct.
* Running basic HDFS and MapReduce commands looks good.

Thanks Masatake.

Thanks & Regards,
Ashutosh


On Fri, May 27, 2022 at 2:15 PM Masatake Iwasaki <
iwasak...@oss.nttdata.co.jp> wrote:

> +1 from myself.
>
> * launched pseudo distributed cluster including kms and httpfs with
> Kerberos and SSL enabled.
>* created encryption zone, put and read files via httpfs.
>* ran example MR wordcount over encryption zone.
>
> * skimmed the contents of site documentation.
>
> * built HBase 1.5.0, Hive 2.3.6 and Spark 2.4.5 against Hadoop 2.10.2 RC0
>on CentOS 7 (x86_64) by using Bigtop branch-1.5 and ran smoke-tests.
>https://github.com/apache/bigtop/pull/906
>
> Masatake Iwasaki
>
> On 2022/05/25 11:40, Masatake Iwasaki wrote:
> > Hi all,
> >
> > Here's Hadoop 2.10.2 release candidate #0:
> >
> > The RC is available at:
> >https://home.apache.org/~iwasakims/hadoop-2.10.2-RC0/
> >
> > The RC tag is at:
> >https://github.com/apache/hadoop/releases/tag/release-2.10.2-RC0
> >
> > The Maven artifacts are staged at:
> >
> https://repository.apache.org/content/repositories/orgapachehadoop-1350
> >
> > You can find my public key at:
> >https://downloads.apache.org/hadoop/common/KEYS
> >
> > Please evaluate the RC and vote.
> > The vote will be open for (at least) 5 days.
> >
> > Thanks,
> > Masatake Iwasaki
> >
> > -
> > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> > For additional commands, e-mail: common-dev-h...@hadoop.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] (YARN-11142) Remove unused Imports in Hadoop YARN project

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11142:
-

 Summary: Remove unused Imports in Hadoop YARN project
 Key: YARN-11142
 URL: https://issues.apache.org/jira/browse/YARN-11142
 Project: Hadoop YARN
  Issue Type: Improvement
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta


h3. Optimize Imports to keep code clean
 # Remove any unused imports



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[jira] [Created] (YARN-11135) Optimize Imports in hadoop project

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11135:
-

 Summary: Optimize Imports in hadoop project
 Key: YARN-11135
 URL: https://issues.apache.org/jira/browse/YARN-11135
 Project: Hadoop YARN
  Issue Type: New Feature
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta


h3. Optimize Imports to keep code clean
 # Remove any unused imports,
 # Sort the import statements.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[jira] [Created] (YARN-11128) Fix comments in TestProportionalCapacityPreemptionPolicy*

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11128:
-

 Summary: Fix comments in TestProportionalCapacityPreemptionPolicy*
 Key: YARN-11128
 URL: https://issues.apache.org/jira/browse/YARN-11128
 Project: Hadoop YARN
  Issue Type: New Feature
  Components: capacityscheduler
Reporter: Ashutosh Gupta


At various places, comment for appsConfig is 

`// queueName\t(priority,resource,host,expression,#repeat,reserved,pending)`

but should be 

`// queueName\t(priority,resource,host,expression,#repeat,reserved,pending)`

 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[jira] [Resolved] (YARN-11124) Backport YARN-6483 to branch-2.10

[Ashutosh Gupta (Jira)]

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

Ashutosh Gupta resolved YARN-11124.
---
Resolution: Duplicate

> Backport YARN-6483 to branch-2.10
> -
>
> Key: YARN-11124
> URL: https://issues.apache.org/jira/browse/YARN-11124
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: yarn
>        Reporter: Ashutosh Gupta
>Priority: Major
>
> Backport YARN-6483 to branch-2.10



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[jira] [Created] (YARN-11125) Backport YARN-6483 to branch-2.10

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11125:
-

 Summary: Backport YARN-6483 to branch-2.10
 Key: YARN-11125
 URL: https://issues.apache.org/jira/browse/YARN-11125
 Project: Hadoop YARN
  Issue Type: Bug
  Components: yarn
Reporter: Ashutosh Gupta


Backport YARN-6483 to branch-2.10



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[jira] [Created] (YARN-11124) Backport YARN-6483 to branch-2.10

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-11124:
-

 Summary: Backport YARN-6483 to branch-2.10
 Key: YARN-11124
 URL: https://issues.apache.org/jira/browse/YARN-11124
 Project: Hadoop YARN
  Issue Type: Bug
  Components: yarn
Reporter: Ashutosh Gupta


Backport YARN-6483 to branch-2.10



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[jira] [Created] (YARN-11119) Backport YARN-10538 to branch-2.10

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-9:
-

 Summary: Backport YARN-10538 to branch-2.10
 Key: YARN-9
 URL: https://issues.apache.org/jira/browse/YARN-9
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.10.0
Reporter: Ashutosh Gupta
Assignee: Ashutosh Gupta


Backport YARN-10538 to branch-2.10



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[jira] [Created] (YARN-10991) Fix to ignore the grouping "[]" properly in parseResourcesString method

[Ashutosh Gupta (Jira)]

Ashutosh Gupta created YARN-10991:
-

 Summary: Fix to ignore the grouping "[]" properly in 
parseResourcesString method
 Key: YARN-10991
 URL: https://issues.apache.org/jira/browse/YARN-10991
 Project: Hadoop YARN
  Issue Type: Bug
  Components: distributed-shell
Affects Versions: 3.3.1
Reporter: Ashutosh Gupta
 Fix For: 3.3.1


Currently if the resourcesStr argument in parseResourcesString method contains 
"]" at the end, its not being ignored. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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