Review request for HADOOP-11875

[Akira Ajisaka]

Hi YARN and MapReduce developers,

I'm working for Java 9 support and created a patch to replace '_' with 
'__' in the hamlet framework (org.apache.hadoop.yarn.webapp.hamlet) used 
by YARN and MapReduce webapp. In Java 9 '_' as a one-character 
identifier is banned.


https://issues.apache.org/jira/browse/HADOOP-11875

In the patch, new package hamlet2 with '__' is created and the old 
package is kept because downstream projects are using hamlet (e.g. 
Apache Slider). And I added a setting for Java 9 not to compile the old 
package.


I'll really appreciate if you will review my patch.

Regards,
Akira

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

[jira] [Created] (YARN-6443) Allow for Priority order relaxing in favor of node locality

[Arun Suresh (JIRA)]

Arun Suresh created YARN-6443:
-

 Summary: Allow for Priority order relaxing in favor of node 
locality 
 Key: YARN-6443
 URL: https://issues.apache.org/jira/browse/YARN-6443
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: capacity scheduler, fairscheduler
Reporter: Arun Suresh
Assignee: Arun Suresh


Currently the Schedulers examine an applications pending Requests in Priority 
order. This JIRA proposes to introduce a flag (either via the 
ApplicationMasterService::registerApplication() or via some Scheduler 
configuration) to favor an ordering that is baised to the node that is 
currently heartbeating by relaxing the priority constraint.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Re: Upgrading minimum version of Maven to 3.1 from 3.0

[Akira Ajisaka]

Agreed to upgrade to 3.3+ and change the version only in trunk.

-Akira

On 2017/04/05 11:21, Sunil G wrote:

Thanks Akira and Junping.

@Junping. Yes, we plan to change this only in trunk and new YARN UI is
available there.
I also feel that there is no issue in moving to a latest version such as
3.3.

+ Sunil

On Tue, Apr 4, 2017 at 11:35 PM Junping Du mailto:j...@hortonworks.com>> wrote:

Thanks Sunil to bring it up. However, any reason not to go to latest
version of maven (3.3+)? Even version 3.1 is quite old - released 3+
years from now (please refer:
https://archive.apache.org/dist/maven/binaries/).
btw, I assume we only plan to change maven version on trunk given
new YARN UI only merge to trunk branch. Isn't it?

Thanks,

Junping

From: Akira Ajisaka mailto:aajis...@apache.org>>
Sent: Monday, April 03, 2017 10:02 PM
To: Sunil G; common-...@hadoop.apache.org
; hdfs-...@hadoop.apache.org
; yarn-dev@hadoop.apache.org
; mapreduce-...@hadoop.apache.org

Subject: Re: Upgrading minimum version of Maven to 3.1 from 3.0

As I mentioned in YARN-6421. I'm +1 for upgrading to 3.1+ because
the latest version of Maven 3.0.x is quite old. (4 years ago)

We need to update dev-support/docker/Dockerfile to enable Maven 3.1+ for
precommit Jenkins job.

Regards,
Akira

On 2017/04/03 18:49, Sunil G wrote:
> Hi Folks,
>
> Recently we were doing build framework up-gradation for Yarn Ui.
In order
> to compile yarn-ui on various architectures, we were using
> frontend-maven-plugin 0.0.22 version.
> However build is failing in *ppc64le.* If we could use latest
version of
> frontend-maven-plugin, we could resolve this error. (such as using 1.1
> version). But this requires maven version 3.1 minimum. YARN-6421 is
> tracking this issue, and we thought we can propose to upgrade to
maven 3.1
>
> Kindly share your thoughts.
>
> Thanks
> + Sunil
>

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org

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




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

Re: Upgrading minimum version of Maven to 3.1 from 3.0

[Sunil G]

Thanks Akira and Junping.

@Junping. Yes, we plan to change this only in trunk and new YARN UI is
available there.
I also feel that there is no issue in moving to a latest version such as
3.3.

+ Sunil

On Tue, Apr 4, 2017 at 11:35 PM Junping Du  wrote:

> Thanks Sunil to bring it up. However, any reason not to go to latest
> version of maven (3.3+)? Even version 3.1 is quite old - released 3+ years
> from now (please refer: https://archive.apache.org/dist/maven/binaries/).
> btw, I assume we only plan to change maven version on trunk given new YARN
> UI only merge to trunk branch. Isn't it?
>
> Thanks,
>
> Junping
> 
> From: Akira Ajisaka 
> Sent: Monday, April 03, 2017 10:02 PM
> To: Sunil G; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> yarn-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org
> Subject: Re: Upgrading minimum version of Maven to 3.1 from 3.0
>
> As I mentioned in YARN-6421. I'm +1 for upgrading to 3.1+ because
> the latest version of Maven 3.0.x is quite old. (4 years ago)
>
> We need to update dev-support/docker/Dockerfile to enable Maven 3.1+ for
> precommit Jenkins job.
>
> Regards,
> Akira
>
> On 2017/04/03 18:49, Sunil G wrote:
> > Hi Folks,
> >
> > Recently we were doing build framework up-gradation for Yarn Ui. In order
> > to compile yarn-ui on various architectures, we were using
> > frontend-maven-plugin 0.0.22 version.
> > However build is failing in *ppc64le.* If we could use latest version of
> > frontend-maven-plugin, we could resolve this error. (such as using 1.1
> > version). But this requires maven version 3.1 minimum. YARN-6421 is
> > tracking this issue, and we thought we can propose to upgrade to maven
> 3.1
> >
> > Kindly share your thoughts.
> >
> > Thanks
> > + Sunil
> >
>
> -
> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
>
>

[jira] [Created] (YARN-6442) Inaccurate javadoc in NodeManagerHardwareUtils.getContainerMemoryMB

[Miklos Szegedi (JIRA)]

Miklos Szegedi created YARN-6442:


 Summary: Inaccurate javadoc in 
NodeManagerHardwareUtils.getContainerMemoryMB
 Key: YARN-6442
 URL: https://issues.apache.org/jira/browse/YARN-6442
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Miklos Szegedi
Priority: Minor


NodeManagerHardwareUtils.getContainerMemoryMB has the following javadoc:
{code}
"If the OS has a
   * ResourceCalculatorPlugin implemented, the calculation is 0.8 * (RAM - 2 *
   * JVM-memory) i.e. use 80% of the memory after accounting for memory used by
   * the DataNode and the NodeManager. If the number is less than 1GB, log a
   * warning message."
{code}
I think the accurate expression is 0.8*(RAM-2*JVM)-systemreserved. I also do 
not see the 1GB cap in the code.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (YARN-6441) Improve UI error message while trying to sort running DAGs with Auto Refresh enabled

[Eric Badger (JIRA)]

Eric Badger created YARN-6441:
-

 Summary: Improve UI error message while trying to sort running 
DAGs with Auto Refresh enabled
 Key: YARN-6441
 URL: https://issues.apache.org/jira/browse/YARN-6441
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Eric Badger
Assignee: Eric Badger






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (YARN-6440) re-visit handling QUEUE-STOP process

[Xuan Gong (JIRA)]

Xuan Gong created YARN-6440:
---

 Summary: re-visit handling QUEUE-STOP process
 Key: YARN-6440
 URL: https://issues.apache.org/jira/browse/YARN-6440
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Xuan Gong
Assignee: Xuan Gong






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Resolved] (YARN-6418) Reduce Resource object creation and overhead in Capacity scheduler inner loop

[Roni Burd (JIRA)]

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

Roni Burd resolved YARN-6418.
-
Resolution: Duplicate

> Reduce Resource object creation and overhead in Capacity scheduler inner loop
> -
>
> Key: YARN-6418
> URL: https://issues.apache.org/jira/browse/YARN-6418
> Project: Hadoop YARN
>  Issue Type: Improvement
>  Components: capacityscheduler, resourcemanager
>Affects Versions: 2.7.3, 3.0.0-alpha2, 2.8
>Reporter: Roni Burd
>Assignee: Roni Burd
>
> Resource object is used multiple due to ResourceCalculator creates new 
> instances on every method call. This gets called several times on each node 
> HB. Resource is a very expensive object that relies on Protobufs 
> The change is to remove the need to use protobuf on the Resource object and 
> avoid creating many objects in the Resource Calculator all the time



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (YARN-6439) Fix ReservationSystem creation of default ReservationQueue

[Carlo Curino (JIRA)]

Carlo Curino created YARN-6439:
--

 Summary: Fix ReservationSystem creation of default ReservationQueue
 Key: YARN-6439
 URL: https://issues.apache.org/jira/browse/YARN-6439
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Carlo Curino
Assignee: Carlo Curino


The ReservationSystem does not create the default ReservationQueue till the 
PlanFollower runs the first time. This is problematic for SLS runs, and might 
show up in some other corner case. Inlining creation of the queue as part of 
PlanQueue creation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

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

[Apache Jenkins Server]

For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/

[Apr 3, 2017 2:35:09 PM] (weichiu) HDFS-11515. -du throws 
ConcurrentModificationException. Contributed by
[Apr 3, 2017 2:57:28 PM] (weichiu) HDFS-11598. Improve -setrep for Erasure 
Coded files. Contributed by
[Apr 3, 2017 6:07:14 PM] (liuml07) HADOOP-14268. Fix markdown itemization in 
hadoop-aws documents.
[Apr 4, 2017 3:13:14 AM] (cdouglas) HADOOP-14271. Correct spelling of 
'occurred' and variants. Contributed




-1 overall


The following subsystems voted -1:
asflicense unit


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


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

Failed junit tests :

   hadoop.security.TestRaceWhenRelogin 
   hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting 
   hadoop.hdfs.server.datanode.TestDataNodeVolumeFailure 
   hadoop.hdfs.server.datanode.checker.TestThrottledAsyncCheckerTimeout 
   hadoop.hdfs.server.datanode.TestDirectoryScanner 
   hadoop.hdfs.security.TestDelegationTokenForProxyUser 
   hadoop.hdfs.TestReadStripedFileWithMissingBlocks 
   hadoop.hdfs.TestBlockStoragePolicy 
   hadoop.hdfs.server.datanode.checker.TestThrottledAsyncChecker 
   hadoop.hdfs.server.datanode.fsdataset.impl.TestSpaceReservation 
   hadoop.hdfs.server.datanode.TestDataNodeUUID 
   hadoop.yarn.server.nodemanager.containermanager.TestContainerManager 
   
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestIncreaseAllocationExpirer
 
   hadoop.yarn.server.resourcemanager.TestRMRestart 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
   hadoop.yarn.server.TestDiskFailures 
   hadoop.yarn.client.api.impl.TestDistributedScheduling 
   hadoop.mapreduce.v2.app.TestMRAppMaster 
   hadoop.mapred.TestMRTimelineEventHandling 
   hadoop.hdfs.TestNNBench 
   hadoop.tools.TestDistCpSystem 

Timed out junit tests :

   org.apache.hadoop.hdfs.TestLeaseRecovery2 
   org.apache.hadoop.mapreduce.v2.TestMRJobs 
  

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/diff-compile-cc-root.txt
  [4.0K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/diff-compile-javac-root.txt
  [184K]

   checkstyle:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/diff-checkstyle-root.txt
  [17M]

   pylint:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/diff-patch-pylint.txt
  [20K]

   shellcheck:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/diff-patch-shellcheck.txt
  [24K]

   shelldocs:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/diff-patch-shelldocs.txt
  [12K]

   whitespace:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/whitespace-eol.txt
  [12M]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/whitespace-tabs.txt
  [1.2M]

   javadoc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/diff-javadoc-javadoc-root.txt
  [2.2M]

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt
  [140K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
  [572K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
  [36K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
  [60K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-tests.txt
  [324K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
  [12K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-app.txt
  [24K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-jobclient.txt
  [88K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86

[jira] [Created] (YARN-6438) Code can be improved in ContainersMonitorImpl.java

[Miklos Szegedi (JIRA)]

Miklos Szegedi created YARN-6438:


 Summary: Code can be improved in ContainersMonitorImpl.java
 Key: YARN-6438
 URL: https://issues.apache.org/jira/browse/YARN-6438
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Reporter: Miklos Szegedi
Priority: Minor


I noticed two code blocks that can be improved in ContainersMonitorImpl.java.  
cpuUsagePercentPerCoreByAllContainers and cpuUsageTotalCoresByAllContainers 
track the same value and CHANGE_MONITORING_CONTAINER_RESOURCE is checked twice 
along with two calls to changeContainerResource.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

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

[Apache Jenkins Server]

For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/

[Apr 3, 2017 2:35:09 PM] (weichiu) HDFS-11515. -du throws 
ConcurrentModificationException. Contributed by
[Apr 3, 2017 2:57:28 PM] (weichiu) HDFS-11598. Improve -setrep for Erasure 
Coded files. Contributed by
[Apr 3, 2017 6:07:14 PM] (liuml07) HADOOP-14268. Fix markdown itemization in 
hadoop-aws documents.
[Apr 4, 2017 3:13:14 AM] (cdouglas) HADOOP-14271. Correct spelling of 
'occurred' and variants. Contributed




-1 overall


The following subsystems voted -1:
compile unit


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


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

Failed junit tests :

   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure180 
   hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer 
   hadoop.hdfs.web.TestWebHdfsTimeouts 
   hadoop.yarn.server.timeline.TestRollingLevelDB 
   hadoop.yarn.server.timeline.TestTimelineDataManager 
   hadoop.yarn.server.timeline.TestLeveldbTimelineStore 
   hadoop.yarn.server.timeline.recovery.TestLeveldbTimelineStateStore 
   hadoop.yarn.server.timeline.TestRollingLevelDBTimelineStore 
   
hadoop.yarn.server.applicationhistoryservice.TestApplicationHistoryServer 
   hadoop.yarn.server.resourcemanager.security.TestDelegationTokenRenewer 
   
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestIncreaseAllocationExpirer
 
   hadoop.yarn.server.resourcemanager.recovery.TestLeveldbRMStateStore 
   hadoop.yarn.server.resourcemanager.TestRMRestart 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.yarn.server.timeline.TestLevelDBCacheTimelineStore 
   hadoop.yarn.server.timeline.TestOverrideTimelineStoreYarnClient 
   hadoop.yarn.server.timeline.TestEntityGroupFSTimelineStore 
   hadoop.yarn.applications.distributedshell.TestDistributedShell 
   hadoop.mapred.TestShuffleHandler 
   hadoop.mapreduce.v2.app.TestRuntimeEstimators 
   hadoop.mapreduce.v2.hs.TestHistoryServerLeveldbStateStoreService 

Timed out junit tests :

   org.apache.hadoop.hdfs.server.blockmanagement.TestBlockStatsMXBean 
   org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCache 
  

   compile:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-compile-root.txt
  [136K]

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-compile-root.txt
  [136K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-compile-root.txt
  [136K]

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
  [208K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
  [16K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-applicationhistoryservice.txt
  [52K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
  [76K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-tests.txt
  [324K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timeline-pluginstorage.txt
  [28K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-applications_hadoop-yarn-applications-distributedshell.txt
  [12K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-ui.txt
  [8.0K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-shuffle.txt
  [8.0K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-app.txt
  [20K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-hs.txt
  [16K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/artifact/ou

[jira] [Created] (YARN-6437) TestSignalContainer#testSignalRequestDeliveryToNM fails intermittently

[Jason Lowe (JIRA)]

Jason Lowe created YARN-6437:


 Summary: TestSignalContainer#testSignalRequestDeliveryToNM fails 
intermittently
 Key: YARN-6437
 URL: https://issues.apache.org/jira/browse/YARN-6437
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Affects Versions: 2.8.0
Reporter: Jason Lowe
Assignee: Jason Lowe


testSignalRequestDeliveryToNM can fail if the containers are returned across 
multiple scheduling heartbeats.  The loop waiting for all the containers should 
be accumulating the containers but instead is smashing the same list of 
containers with whatever the allocate call returns.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Re: Upgrading minimum version of Maven to 3.1 from 3.0

[Junping Du]

Thanks Sunil to bring it up. However, any reason not to go to latest version of 
maven (3.3+)? Even version 3.1 is quite old - released 3+ years from now 
(please refer: https://archive.apache.org/dist/maven/binaries/).
btw, I assume we only plan to change maven version on trunk given new YARN UI 
only merge to trunk branch. Isn't it?

Thanks,

Junping

From: Akira Ajisaka 
Sent: Monday, April 03, 2017 10:02 PM
To: Sunil G; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
yarn-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Subject: Re: Upgrading minimum version of Maven to 3.1 from 3.0

As I mentioned in YARN-6421. I'm +1 for upgrading to 3.1+ because
the latest version of Maven 3.0.x is quite old. (4 years ago)

We need to update dev-support/docker/Dockerfile to enable Maven 3.1+ for
precommit Jenkins job.

Regards,
Akira

On 2017/04/03 18:49, Sunil G wrote:
> Hi Folks,
>
> Recently we were doing build framework up-gradation for Yarn Ui. In order
> to compile yarn-ui on various architectures, we were using
> frontend-maven-plugin 0.0.22 version.
> However build is failing in *ppc64le.* If we could use latest version of
> frontend-maven-plugin, we could resolve this error. (such as using 1.1
> version). But this requires maven version 3.1 minimum. YARN-6421 is
> tracking this issue, and we thought we can propose to upgrade to maven 3.1
>
> Kindly share your thoughts.
>
> Thanks
> + Sunil
>

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


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

[jira] [Created] (YARN-6436) TestSchedulingPolicy#testParseSchedulingPolicy timeout is too low

[Jason Lowe (JIRA)]

Jason Lowe created YARN-6436:


 Summary: TestSchedulingPolicy#testParseSchedulingPolicy timeout is 
too low
 Key: YARN-6436
 URL: https://issues.apache.org/jira/browse/YARN-6436
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Reporter: Jason Lowe


The timeout for testParseSchedulingPolicy is only one second.  An I/O hiccup on 
a VM can make this test fail for the wrong reasons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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