[jira] [Updated] (YARN-1673) Valid yarn kill application prints out help message.
[ https://issues.apache.org/jira/browse/YARN-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-1673: Attachment: YARN-1673.patch Attaching trivial patch Thanks, Mayank Valid yarn kill application prints out help message. Key: YARN-1673 URL: https://issues.apache.org/jira/browse/YARN-1673 Project: Hadoop YARN Issue Type: Bug Components: client Affects Versions: 2.4.0 Reporter: Tassapol Athiapinya Assignee: Mayank Bansal Priority: Blocker Attachments: YARN-1673.patch, YARN-1673.txt yarn application -kill application ID used to work previously. In 2.4.0 it prints out help message and does not kill the application. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1673) Valid yarn kill application prints out help message.
[
https://issues.apache.org/jira/browse/YARN-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889310#comment-13889310
]
Hadoop QA commented on YARN-1673:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626616/YARN-1673.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client:
org.apache.hadoop.yarn.client.cli.TestYarnCLI
The following test timeouts occurred in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client:
org.apache.hadoop.yarn.client.api.impl.TestNMClient
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2989//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2989//console
This message is automatically generated.
Valid yarn kill application prints out help message.
Key: YARN-1673
URL: https://issues.apache.org/jira/browse/YARN-1673
Project: Hadoop YARN
Issue Type: Bug
Components: client
Affects Versions: 2.4.0
Reporter: Tassapol Athiapinya
Assignee: Mayank Bansal
Priority: Blocker
Attachments: YARN-1673.patch, YARN-1673.txt
yarn application -kill application ID
used to work previously. In 2.4.0 it prints out help message and does not
kill the application.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1611) Make admin refresh of capacity scheduler configuration work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889758#comment-13889758 ] Vinod Kumar Vavilapalli commented on YARN-1611: --- Looks good, +1. Checking this in. Make admin refresh of capacity scheduler configuration work across RM failover -- Key: YARN-1611 URL: https://issues.apache.org/jira/browse/YARN-1611 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Attachments: YARN-1611.1.patch, YARN-1611.10.patch, YARN-1611.2.patch, YARN-1611.2.patch, YARN-1611.3.patch, YARN-1611.3.patch, YARN-1611.4.patch, YARN-1611.5.patch, YARN-1611.6.patch, YARN-1611.7.patch, YARN-1611.8.patch, YARN-1611.9.patch, YARN-1611.9.patch Currently, If we do refresh* for a standby RM, it will failover to the current active RM, and do the refresh* based on the local configuration file of the active RM. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1553) Do not use HttpConfig.isSecure() in YARN
[
https://issues.apache.org/jira/browse/YARN-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai updated YARN-1553:
-
Attachment: YARN-1553.002.patch
Rebase
Do not use HttpConfig.isSecure() in YARN
Key: YARN-1553
URL: https://issues.apache.org/jira/browse/YARN-1553
Project: Hadoop YARN
Issue Type: Bug
Reporter: Haohui Mai
Assignee: Haohui Mai
Attachments: YARN-1553.000.patch, YARN-1553.001.patch,
YARN-1553.002.patch
HDFS-5305 and related jira decide that each individual project will have
their own configuration on http policy. {{HttpConfig.isSecure}} is a global
static method which does not fit the design anymore. The same functionality
should be moved into the YARN code base.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1668) Make admin refreshAdminAcls work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1668: Attachment: YARN-1668.3.patch Make admin refreshAdminAcls work across RM failover --- Key: YARN-1668 URL: https://issues.apache.org/jira/browse/YARN-1668 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Attachments: YARN-1668.1.patch, YARN-1668.2.patch, YARN-1668.3.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1611) Make admin refresh of capacity scheduler configuration work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889784#comment-13889784 ] Hudson commented on YARN-1611: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5094 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5094/]) YARN-1611. Introduced the concept of a configuration provider which can be used by ResourceManager to read configuration locally or from remote systems so as to help RM failover. Contributed by Xuan Gong. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564002) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/ConfigurationProvider.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/ConfigurationProviderFactory.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/FileSystemBasedConfigurationProvider.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/LocalConfigurationProvider.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/AdminService.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacitySchedulerConfiguration.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMAdminService.java Make admin refresh of capacity scheduler configuration work across RM failover -- Key: YARN-1611 URL: https://issues.apache.org/jira/browse/YARN-1611 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Fix For: 2.4.0 Attachments: YARN-1611.1.patch, YARN-1611.10.patch, YARN-1611.2.patch, YARN-1611.2.patch, YARN-1611.3.patch, YARN-1611.3.patch, YARN-1611.4.patch, YARN-1611.5.patch, YARN-1611.6.patch, YARN-1611.7.patch, YARN-1611.8.patch, YARN-1611.9.patch, YARN-1611.9.patch Currently, If we do refresh* for a standby RM, it will failover to the current active RM, and do the refresh* based on the local configuration file of the active RM. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1578) Fix how to read history file in FileSystemApplicationHistoryStore
[
https://issues.apache.org/jira/browse/YARN-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889782#comment-13889782
]
Zhijie Shen commented on YARN-1578:
---
[~sinchii], thanks for the patch, which I thinks has found the buggy code to
fix. I've some comments on the fix:
1. Please refer to getContainer(). We should still merge partial information
into container history data object when we only have the start/finish data. The
get APIs should be tolerant for missing information.
2. getApplicationAttempts need to be fixed as well.
3. Please create some test cases to imitate missing partial data, and the get
APIs still work.
Fix how to read history file in FileSystemApplicationHistoryStore
-
Key: YARN-1578
URL: https://issues.apache.org/jira/browse/YARN-1578
Project: Hadoop YARN
Issue Type: Sub-task
Affects Versions: YARN-321
Reporter: Shinichi Yamashita
Assignee: Shinichi Yamashita
Attachments: YARN-1578-2.patch, YARN-1578.patch,
application_1390978867235_0001, resoucemanager.log, screenshot.png,
screenshot2.pdf
I carried out PiEstimator job at Hadoop cluster which applied YARN-321.
After the job end and when I accessed Web UI of HistoryServer, it displayed
500. And HistoryServer daemon log was output as follows.
{code}
2014-01-09 13:31:12,227 ERROR org.apache.hadoop.yarn.webapp.Dispatcher: error
handling URI:
/applicationhistory/appattempt/appattempt_1389146249925_0008_01
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hadoop.yarn.webapp.Dispatcher.service(Dispatcher.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
(snip...)
Caused by: java.lang.NullPointerException
at
org.apache.hadoop.yarn.server.applicationhistoryservice.FileSystemApplicationHistoryStore.mergeContainerHistoryData(FileSystemApplicationHistoryStore.java:696)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.FileSystemApplicationHistoryStore.getContainers(FileSystemApplicationHistoryStore.java:429)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryManagerImpl.getContainers(ApplicationHistoryManagerImpl.java:201)
at
org.apache.hadoop.yarn.server.webapp.AppAttemptBlock.render(AppAttemptBlock.java:110)
(snip...)
{code}
I confirmed that there was container which was not finished from
ApplicationHistory file.
In ResourceManager daemon log, ResourceManager reserved this container, but
did not allocate it.
When FileSystemApplicationHistoryStore reads container information without
finish data in history file, this problem occurs.
In consideration of the case which there is not finish data, we should fix
how to read history file in FileSystemApplicationHistoryStore.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1659) Define ApplicationTimelineStore interface and store-facing entity, entity-info and event objects
[ https://issues.apache.org/jira/browse/YARN-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889797#comment-13889797 ] Zhijie Shen commented on YARN-1659: --- +1, LGTM as well Define ApplicationTimelineStore interface and store-facing entity, entity-info and event objects Key: YARN-1659 URL: https://issues.apache.org/jira/browse/YARN-1659 Project: Hadoop YARN Issue Type: Sub-task Reporter: Billie Rinaldi Assignee: Billie Rinaldi Attachments: YARN-1659-1.patch, YARN-1659-3.patch, YARN-1659-4.patch, YARN-1659-5.patch, YARN-1659-6.patch, YARN-1659-7.patch, YARN-1659.2.patch These will be used by ApplicationTimelineStore interface. The web services will convert the store-facing obects to the user-facing objects. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1498) Common scheduler changes for moving apps between queues
[ https://issues.apache.org/jira/browse/YARN-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889814#comment-13889814 ] Hudson commented on YARN-1498: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5095 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5095/]) YARN-1498 addendum to fix findbugs warning (sandy: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564018) * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerApplicationAttempt.java Common scheduler changes for moving apps between queues --- Key: YARN-1498 URL: https://issues.apache.org/jira/browse/YARN-1498 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Affects Versions: 2.2.0 Reporter: Sandy Ryza Assignee: Sandy Ryza Fix For: 3.0.0 Attachments: YARN-1498-1.patch, YARN-1498-addendum.patch, YARN-1498.patch, YARN-1498.patch This JIRA is to track changes that aren't in particular schedulers but that help them support moving apps between queues. In particular, it makes sure that QueueMetrics are properly updated when an app changes queue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1639) YARM RM HA requires different configs on different RM hosts
[ https://issues.apache.org/jira/browse/YARN-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889825#comment-13889825 ] Vinod Kumar Vavilapalli commented on YARN-1639: --- bq. Yes, it is possible to return null. But this can be verified in verifyAndSetCurrentRMHAId(). If getRMHAId() is return null, it will throw out an exception Yeah, I checked all the code-paths. This validation happens upfront in the RM so all the remaining callers are fine. There should be a better way to structure it, but it seems fine for now. The patch looks good to me. +1. Checking this in. YARM RM HA requires different configs on different RM hosts --- Key: YARN-1639 URL: https://issues.apache.org/jira/browse/YARN-1639 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Reporter: Arpit Gupta Assignee: Xuan Gong Attachments: YARN-1639.1.patch, YARN-1639.2.patch, YARN-1639.3.patch, YARN-1639.4.patch, YARN-1639.5.patch We need to set yarn.resourcemanager.ha.id to rm1 or rm2 based on which rm you want to first or second. This means we have different configs on different RM nodes. This is unlike HDFS HA where the same configs are pushed to both NN's and it would be better to have the same setup for RM as this would make installation and managing easier. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1506) Replace set resource change on RMNode/SchedulerNode directly with event notification.
[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1506: Target Version/s: 2.4.0 (was: 2.3.0) Replace set resource change on RMNode/SchedulerNode directly with event notification. - Key: YARN-1506 URL: https://issues.apache.org/jira/browse/YARN-1506 Project: Hadoop YARN Issue Type: Sub-task Components: nodemanager, scheduler Reporter: Junping Du Assignee: Junping Du Priority: Blocker Attachments: YARN-1506-v1.patch, YARN-1506-v2.patch, YARN-1506-v3.patch, YARN-1506-v4.patch, YARN-1506-v5.patch, YARN-1506-v6.patch According to Vinod's comments on YARN-312 (https://issues.apache.org/jira/browse/YARN-312?focusedCommentId=13846087page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13846087), we should replace RMNode.setResourceOption() with some resource change event. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1506) Replace set resource change on RMNode/SchedulerNode directly with event notification.
[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889832#comment-13889832 ] Arun C Murthy commented on YARN-1506: - Moving to 2.4.0, doesn't look like a blocker to me since the feature is still incomplete. Thanks. Replace set resource change on RMNode/SchedulerNode directly with event notification. - Key: YARN-1506 URL: https://issues.apache.org/jira/browse/YARN-1506 Project: Hadoop YARN Issue Type: Sub-task Components: nodemanager, scheduler Reporter: Junping Du Assignee: Junping Du Priority: Blocker Attachments: YARN-1506-v1.patch, YARN-1506-v2.patch, YARN-1506-v3.patch, YARN-1506-v4.patch, YARN-1506-v5.patch, YARN-1506-v6.patch According to Vinod's comments on YARN-312 (https://issues.apache.org/jira/browse/YARN-312?focusedCommentId=13846087page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13846087), we should replace RMNode.setResourceOption() with some resource change event. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1659) Define ApplicationTimelineStore interface and store-facing entity, entity-info and event objects
[
https://issues.apache.org/jira/browse/YARN-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889833#comment-13889833
]
Hadoop QA commented on YARN-1659:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626530/YARN-1659-7.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2991//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2991//console
This message is automatically generated.
Define ApplicationTimelineStore interface and store-facing entity,
entity-info and event objects
Key: YARN-1659
URL: https://issues.apache.org/jira/browse/YARN-1659
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Billie Rinaldi
Assignee: Billie Rinaldi
Attachments: YARN-1659-1.patch, YARN-1659-3.patch, YARN-1659-4.patch,
YARN-1659-5.patch, YARN-1659-6.patch, YARN-1659-7.patch, YARN-1659.2.patch
These will be used by ApplicationTimelineStore interface. The web services
will convert the store-facing obects to the user-facing objects.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1399) Allow users to annotate an application with multiple tags
[ https://issues.apache.org/jira/browse/YARN-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889845#comment-13889845 ] Vinod Kumar Vavilapalli commented on YARN-1399: --- So, if adding new API is too much to do now, we can stick to what we said earlier [here|https://issues.apache.org/jira/browse/YARN-1399?focusedCommentId=13868349page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13868349]. We can add such a new API anytime. So let's unblock this JIRA and yes, default to ALL, and Oozie set it to use OWN. Allow users to annotate an application with multiple tags - Key: YARN-1399 URL: https://issues.apache.org/jira/browse/YARN-1399 Project: Hadoop YARN Issue Type: Improvement Reporter: Zhijie Shen Nowadays, when submitting an application, users can fill the applicationType field to facilitate searching it later. IMHO, it's good to accept multiple tags to allow users to describe their applications in multiple aspects, including the application type. Then, searching by tags may be more efficient for users to reach their desired application collection. It's pretty much like the tag system of online photo/video/music and etc. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1639) YARM RM HA requires different configs on different RM hosts
[ https://issues.apache.org/jira/browse/YARN-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889847#comment-13889847 ] Hudson commented on YARN-1639: -- FAILURE: Integrated in Hadoop-trunk-Commit #5096 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5096/]) YARN-1639. Modified RM HA configuration handling to have a way of not requiring separate configuration files for each RM. Contributed by Xuan Gong. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564032) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/HAUtil.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMHA.java YARM RM HA requires different configs on different RM hosts --- Key: YARN-1639 URL: https://issues.apache.org/jira/browse/YARN-1639 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Reporter: Arpit Gupta Assignee: Xuan Gong Fix For: 2.4.0 Attachments: YARN-1639.1.patch, YARN-1639.2.patch, YARN-1639.3.patch, YARN-1639.4.patch, YARN-1639.5.patch We need to set yarn.resourcemanager.ha.id to rm1 or rm2 based on which rm you want to first or second. This means we have different configs on different RM nodes. This is unlike HDFS HA where the same configs are pushed to both NN's and it would be better to have the same setup for RM as this would make installation and managing easier. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1659) Define the ApplicationTimelineStore store as an abstraction for implementing different storage impls for storing timeline information
[ https://issues.apache.org/jira/browse/YARN-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1659: -- Summary: Define the ApplicationTimelineStore store as an abstraction for implementing different storage impls for storing timeline information (was: Define ApplicationTimelineStore interface and store-facing entity, entity-info and event objects) Define the ApplicationTimelineStore store as an abstraction for implementing different storage impls for storing timeline information - Key: YARN-1659 URL: https://issues.apache.org/jira/browse/YARN-1659 Project: Hadoop YARN Issue Type: Sub-task Reporter: Billie Rinaldi Assignee: Billie Rinaldi Fix For: 2.4.0 Attachments: YARN-1659-1.patch, YARN-1659-3.patch, YARN-1659-4.patch, YARN-1659-5.patch, YARN-1659-6.patch, YARN-1659-7.patch, YARN-1659.2.patch These will be used by ApplicationTimelineStore interface. The web services will convert the store-facing obects to the user-facing objects. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1668) Make admin refreshAdminAcls work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889857#comment-13889857 ] Vinod Kumar Vavilapalli commented on YARN-1668: --- The patch looks good to me. +1. Checking this in. Make admin refreshAdminAcls work across RM failover --- Key: YARN-1668 URL: https://issues.apache.org/jira/browse/YARN-1668 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Attachments: YARN-1668.1.patch, YARN-1668.2.patch, YARN-1668.3.patch Change the handling of admin-acls to be available across RM failover by making using of a remote configuration-provider -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1668) Make admin refreshAdminAcls work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1668: -- Description: Change the handling of admin-acls to be available across RM failover by making using of a remote configuration-provider Make admin refreshAdminAcls work across RM failover --- Key: YARN-1668 URL: https://issues.apache.org/jira/browse/YARN-1668 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Attachments: YARN-1668.1.patch, YARN-1668.2.patch, YARN-1668.3.patch Change the handling of admin-acls to be available across RM failover by making using of a remote configuration-provider -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1659) Define the ApplicationTimelineStore store as an abstraction for implementing different storage impls for storing timeline information
[ https://issues.apache.org/jira/browse/YARN-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889864#comment-13889864 ] Hudson commented on YARN-1659: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5097 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5097/]) YARN-1659. Defined the ApplicationTimelineStore store as an abstraction for implementing different storage impls for storing timeline information. Contributed by Billie Rinaldi. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564037) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/apptimeline/ATSEntity.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/apptimeline/ATSEvent.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/apptimeline/ATSEvents.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/apptimeline/ATSPutErrors.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/api/records/apptimeline/TestApplicationTimelineRecords.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/apptimeline * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/apptimeline/ApplicationTimelineReader.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/apptimeline/ApplicationTimelineStore.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/apptimeline/ApplicationTimelineWriter.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/apptimeline/NameValuePair.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/apptimeline/package-info.java Define the ApplicationTimelineStore store as an abstraction for implementing different storage impls for storing timeline information - Key: YARN-1659 URL: https://issues.apache.org/jira/browse/YARN-1659 Project: Hadoop YARN Issue Type: Sub-task Reporter: Billie Rinaldi Assignee: Billie Rinaldi Fix For: 2.4.0 Attachments: YARN-1659-1.patch, YARN-1659-3.patch, YARN-1659-4.patch, YARN-1659-5.patch, YARN-1659-6.patch, YARN-1659-7.patch, YARN-1659.2.patch These will be used by ApplicationTimelineStore interface. The web services will convert the store-facing obects to the user-facing objects. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1668) Make admin refreshAdminAcls work across RM failover
[
https://issues.apache.org/jira/browse/YARN-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889852#comment-13889852
]
Hadoop QA commented on YARN-1668:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626714/YARN-1668.3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2990//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2990//console
This message is automatically generated.
Make admin refreshAdminAcls work across RM failover
---
Key: YARN-1668
URL: https://issues.apache.org/jira/browse/YARN-1668
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Xuan Gong
Assignee: Xuan Gong
Attachments: YARN-1668.1.patch, YARN-1668.2.patch, YARN-1668.3.patch
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1668) Make admin refreshAdminAcls work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889881#comment-13889881 ] Hudson commented on YARN-1668: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5098 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5098/]) YARN-1668. Modified RM HA handling of admin-acls to be available across RM failover by making using of a remote configuration-provider. Contributed by Xuan Gong. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564043) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/AdminService.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMAdminService.java Make admin refreshAdminAcls work across RM failover --- Key: YARN-1668 URL: https://issues.apache.org/jira/browse/YARN-1668 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Fix For: 2.4.0 Attachments: YARN-1668.1.patch, YARN-1668.2.patch, YARN-1668.3.patch Change the handling of admin-acls to be available across RM failover by making using of a remote configuration-provider -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1667) Make admin refreshSuperUserGroupsConfiguration work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1667: Attachment: YARN-1667.3.patch Make admin refreshSuperUserGroupsConfiguration work across RM failover -- Key: YARN-1667 URL: https://issues.apache.org/jira/browse/YARN-1667 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Attachments: YARN-1667.1.patch, YARN-1667.2.patch, YARN-1667.3.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1479) Invalid NaN values in Hadoop REST API JSON response
[ https://issues.apache.org/jira/browse/YARN-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-1479: -- Attachment: Yarn-1479v2.patch Invalid NaN values in Hadoop REST API JSON response --- Key: YARN-1479 URL: https://issues.apache.org/jira/browse/YARN-1479 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 0.23.6, 2.0.4-alpha Reporter: Kendall Thrapp Assignee: Chen He Fix For: 2.3.0 Attachments: Yarn-1479.patch, Yarn-1479v2.patch I've been occasionally coming across instances where Hadoop's Cluster Applications REST API (http://hadoop.apache.org/docs/r0.23.6/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API) has returned JSON that PHP's json_decode function failed to parse. I've tracked the syntax error down to the presence of the unquoted word NaN appearing as a value in the JSON. For example: progress:NaN, NaN is not part of the JSON spec, so its presence renders the whole JSON string invalid. Hadoop needs to return something other than NaN in this case -- perhaps an empty string or the quoted string NaN. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1479) Invalid NaN values in Hadoop REST API JSON response
[ https://issues.apache.org/jira/browse/YARN-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-1479: -- Fix Version/s: (was: 2.3.0) Invalid NaN values in Hadoop REST API JSON response --- Key: YARN-1479 URL: https://issues.apache.org/jira/browse/YARN-1479 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 0.23.6, 2.0.4-alpha Reporter: Kendall Thrapp Assignee: Chen He Attachments: Yarn-1479.patch, Yarn-1479v2.patch I've been occasionally coming across instances where Hadoop's Cluster Applications REST API (http://hadoop.apache.org/docs/r0.23.6/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API) has returned JSON that PHP's json_decode function failed to parse. I've tracked the syntax error down to the presence of the unquoted word NaN appearing as a value in the JSON. For example: progress:NaN, NaN is not part of the JSON spec, so its presence renders the whole JSON string invalid. Hadoop needs to return something other than NaN in this case -- perhaps an empty string or the quoted string NaN. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1635) Implement a Leveldb based ApplicationTimelineStore
[ https://issues.apache.org/jira/browse/YARN-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billie Rinaldi updated YARN-1635: - Attachment: YARN-1635.4.patch Implement a Leveldb based ApplicationTimelineStore -- Key: YARN-1635 URL: https://issues.apache.org/jira/browse/YARN-1635 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Billie Rinaldi Attachments: YARN-1635.1.patch, YARN-1635.2.patch, YARN-1635.3.patch, YARN-1635.4.patch As per the design doc, we need a levelDB + local-filesystem based implementation to start with and for small deployments. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1479) Invalid NaN values in Hadoop REST API JSON response
[
https://issues.apache.org/jira/browse/YARN-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889944#comment-13889944
]
Hadoop QA commented on YARN-1479:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626738/Yarn-1479v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2994//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2994//console
This message is automatically generated.
Invalid NaN values in Hadoop REST API JSON response
---
Key: YARN-1479
URL: https://issues.apache.org/jira/browse/YARN-1479
Project: Hadoop YARN
Issue Type: Improvement
Affects Versions: 0.23.6, 2.0.4-alpha
Reporter: Kendall Thrapp
Assignee: Chen He
Attachments: Yarn-1479.patch, Yarn-1479v2.patch
I've been occasionally coming across instances where Hadoop's Cluster
Applications REST API
(http://hadoop.apache.org/docs/r0.23.6/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API)
has returned JSON that PHP's json_decode function failed to parse. I've
tracked the syntax error down to the presence of the unquoted word NaN
appearing as a value in the JSON. For example:
progress:NaN,
NaN is not part of the JSON spec, so its presence renders the whole JSON
string invalid. Hadoop needs to return something other than NaN in this case
-- perhaps an empty string or the quoted string NaN.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1667) Make admin refreshSuperUserGroupsConfiguration work across RM failover
[
https://issues.apache.org/jira/browse/YARN-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889952#comment-13889952
]
Hadoop QA commented on YARN-1667:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626735/YARN-1667.3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2993//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2993//console
This message is automatically generated.
Make admin refreshSuperUserGroupsConfiguration work across RM failover
--
Key: YARN-1667
URL: https://issues.apache.org/jira/browse/YARN-1667
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Xuan Gong
Assignee: Xuan Gong
Attachments: YARN-1667.1.patch, YARN-1667.2.patch, YARN-1667.3.patch
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1639) YARM RM HA requires different configs on different RM hosts
[ https://issues.apache.org/jira/browse/YARN-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889966#comment-13889966 ] Bikas Saha commented on YARN-1639: -- After this patch, if there are 4 RM's in HA setup, then do we have to enumerate all RM instance configs in the conf file. ie. for RM Admin Service RPC port we need to have 4 entries suffixed by each RM id (the values may be identical)? Was this the case earlier too? Or earlier, we could have specified an single config for RM Admin Service RPC and each RM would use its rm id to create a suffixed entry in the config from the single config. YARM RM HA requires different configs on different RM hosts --- Key: YARN-1639 URL: https://issues.apache.org/jira/browse/YARN-1639 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Reporter: Arpit Gupta Assignee: Xuan Gong Fix For: 2.4.0 Attachments: YARN-1639.1.patch, YARN-1639.2.patch, YARN-1639.3.patch, YARN-1639.4.patch, YARN-1639.5.patch We need to set yarn.resourcemanager.ha.id to rm1 or rm2 based on which rm you want to first or second. This means we have different configs on different RM nodes. This is unlike HDFS HA where the same configs are pushed to both NN's and it would be better to have the same setup for RM as this would make installation and managing easier. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1553) Do not use HttpConfig.isSecure() in YARN
[
https://issues.apache.org/jira/browse/YARN-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889974#comment-13889974
]
Hadoop QA commented on YARN-1553:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626713/YARN-1553.002.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy:
org.apache.hadoop.mapreduce.v2.app.TestRMContainerAllocator
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesApps
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestZKRMStateStore
org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.TestRMContainerImpl
org.apache.hadoop.yarn.server.TestMiniYARNClusterForHA
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2992//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/2992//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2992//console
This message is automatically generated.
Do not use HttpConfig.isSecure() in YARN
Key: YARN-1553
URL: https://issues.apache.org/jira/browse/YARN-1553
Project: Hadoop YARN
Issue Type: Bug
Reporter: Haohui Mai
Assignee: Haohui Mai
Attachments: YARN-1553.000.patch, YARN-1553.001.patch,
YARN-1553.002.patch
HDFS-5305 and related jira decide that each individual project will have
their own configuration on http policy. {{HttpConfig.isSecure}} is a global
static method which does not fit the design anymore. The same functionality
should be moved into the YARN code base.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1667) Make admin refreshSuperUserGroupsConfiguration work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889980#comment-13889980 ] Vinod Kumar Vavilapalli commented on YARN-1667: --- +1, looks good. Checking this in. Make admin refreshSuperUserGroupsConfiguration work across RM failover -- Key: YARN-1667 URL: https://issues.apache.org/jira/browse/YARN-1667 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Attachments: YARN-1667.1.patch, YARN-1667.2.patch, YARN-1667.3.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1639) YARM RM HA requires different configs on different RM hosts
[ https://issues.apache.org/jira/browse/YARN-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889978#comment-13889978 ] Xuan Gong commented on YARN-1639: - bq. After this patch, if there are 4 RM's in HA setup, then do we have to enumerate all RM instance configs in the conf file. ie. for RM Admin Service RPC port we need to have 4 entries suffixed by each RM id (the values may be identical)? Was this the case earlier too? Or earlier, we could have specified an single config for RM Admin Service RPC and each RM would use its rm id to create a suffixed entry in the config from the single config. Before this patch, if we want to config HA, we need to have yarn.resourcemanager.ha.rm-ids : rm1, rm2, rm3, rm4 And we need to set yarn.resourcemanager.ha.id to rm1 or rm2 or rm3 or rm4 for four different configurations Then we should provide all RM rpc addresses suffixed by each RM id for all four different configurations. After this patch, we do not need to provide any yarn.resourcemanager.ha.id, other configurations are the same. In that case, we can share the same configuration for the different machines. So, we do not provide yarn.resourcemanager.ha.id, and the rm figures out its own rm_id by comparing its local address with RM_Address. These is one thing we need to pay attention is that we can not launch more than one rm in one single machine. If we really want to do that (for example, do the testing, miniYarnCluster), we need to set values for yarn.resourcemanager.ha.id YARM RM HA requires different configs on different RM hosts --- Key: YARN-1639 URL: https://issues.apache.org/jira/browse/YARN-1639 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Reporter: Arpit Gupta Assignee: Xuan Gong Fix For: 2.4.0 Attachments: YARN-1639.1.patch, YARN-1639.2.patch, YARN-1639.3.patch, YARN-1639.4.patch, YARN-1639.5.patch We need to set yarn.resourcemanager.ha.id to rm1 or rm2 based on which rm you want to first or second. This means we have different configs on different RM nodes. This is unlike HDFS HA where the same configs are pushed to both NN's and it would be better to have the same setup for RM as this would make installation and managing easier. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1667) Make admin refreshSuperUserGroupsConfiguration work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889989#comment-13889989 ] Hudson commented on YARN-1667: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5099 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5099/]) YARN-1667. Modified RM HA handling of super users (with proxying ability) to be available across RM failover by making using of a remote configuration-provider. Contributed by Xuan Gong. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564100) * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/authorize/ProxyUsers.java * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/AdminService.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMAdminService.java Make admin refreshSuperUserGroupsConfiguration work across RM failover -- Key: YARN-1667 URL: https://issues.apache.org/jira/browse/YARN-1667 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Fix For: 2.4.0 Attachments: YARN-1667.1.patch, YARN-1667.2.patch, YARN-1667.3.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1628) TestContainerManagerSecurity fails on trunk
[
https://issues.apache.org/jira/browse/YARN-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-1628:
--
Attachment: YARN-1628.1.patch
Patch adding core-site.xml with IP checks disabled. This is similar to what we
eventually did at MAPREDUCE-5261. The test failed before the patch and passes
after it is applied.
TestContainerManagerSecurity fails on trunk
---
Key: YARN-1628
URL: https://issues.apache.org/jira/browse/YARN-1628
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 3.0.0, 2.2.0
Reporter: Mit Desai
Assignee: Mit Desai
Attachments: YARN-1628.1.patch, YARN-1628.patch
The Test fails with the following error
{noformat}
java.lang.IllegalArgumentException: java.net.UnknownHostException: InvalidHost
at
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:377)
at
org.apache.hadoop.yarn.server.security.BaseNMTokenSecretManager.newInstance(BaseNMTokenSecretManager.java:145)
at
org.apache.hadoop.yarn.server.security.BaseNMTokenSecretManager.createNMToken(BaseNMTokenSecretManager.java:136)
at
org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testNMTokens(TestContainerManagerSecurity.java:253)
at
org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testContainerManager(TestContainerManagerSecurity.java:144)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1635) Implement a Leveldb based ApplicationTimelineStore
[
https://issues.apache.org/jira/browse/YARN-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890023#comment-13890023
]
Hadoop QA commented on YARN-1635:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626739/YARN-1635.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 1548 javac
compiler warnings (more than the trunk's current 1545 warnings).
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 4 new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1
release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2995//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/2995//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/2995//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-applicationhistoryservice.html
Javac warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/2995//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2995//console
This message is automatically generated.
Implement a Leveldb based ApplicationTimelineStore
--
Key: YARN-1635
URL: https://issues.apache.org/jira/browse/YARN-1635
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Vinod Kumar Vavilapalli
Assignee: Billie Rinaldi
Attachments: YARN-1635.1.patch, YARN-1635.2.patch, YARN-1635.3.patch,
YARN-1635.4.patch
As per the design doc, we need a levelDB + local-filesystem based
implementation to start with and for small deployments.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1553) Do not use HttpConfig.isSecure() in YARN
[
https://issues.apache.org/jira/browse/YARN-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai updated YARN-1553:
-
Attachment: YARN-1553.003.patch
The v3 patch fixes the failed unit tests.
Do not use HttpConfig.isSecure() in YARN
Key: YARN-1553
URL: https://issues.apache.org/jira/browse/YARN-1553
Project: Hadoop YARN
Issue Type: Bug
Reporter: Haohui Mai
Assignee: Haohui Mai
Attachments: YARN-1553.000.patch, YARN-1553.001.patch,
YARN-1553.002.patch, YARN-1553.003.patch
HDFS-5305 and related jira decide that each individual project will have
their own configuration on http policy. {{HttpConfig.isSecure}} is a global
static method which does not fit the design anymore. The same functionality
should be moved into the YARN code base.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1497) Expose moving apps between queues on the command line
[ https://issues.apache.org/jira/browse/YARN-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1497: - Attachment: YARN-1497.patch Expose moving apps between queues on the command line - Key: YARN-1497 URL: https://issues.apache.org/jira/browse/YARN-1497 Project: Hadoop YARN Issue Type: Sub-task Components: client Affects Versions: 2.2.0 Reporter: Sandy Ryza Assignee: Sandy Ryza Attachments: YARN-1497.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1628) TestContainerManagerSecurity fails on trunk
[
https://issues.apache.org/jira/browse/YARN-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890063#comment-13890063
]
Hadoop QA commented on YARN-1628:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626752/YARN-1628.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2997//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2997//console
This message is automatically generated.
TestContainerManagerSecurity fails on trunk
---
Key: YARN-1628
URL: https://issues.apache.org/jira/browse/YARN-1628
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 3.0.0, 2.2.0
Reporter: Mit Desai
Assignee: Mit Desai
Attachments: YARN-1628.1.patch, YARN-1628.patch
The Test fails with the following error
{noformat}
java.lang.IllegalArgumentException: java.net.UnknownHostException: InvalidHost
at
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:377)
at
org.apache.hadoop.yarn.server.security.BaseNMTokenSecretManager.newInstance(BaseNMTokenSecretManager.java:145)
at
org.apache.hadoop.yarn.server.security.BaseNMTokenSecretManager.createNMToken(BaseNMTokenSecretManager.java:136)
at
org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testNMTokens(TestContainerManagerSecurity.java:253)
at
org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testContainerManager(TestContainerManagerSecurity.java:144)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1637: -- Attachment: YARN-1637.3.patch Upload a new patch, which rebased the code with following more changes: 1. Update the deprecated methods in YarnJacksonJaxbJsonProvider. 2. Make entity to implement Comparable as well, and update the javadoc Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1673) Valid yarn kill application prints out help message.
[ https://issues.apache.org/jira/browse/YARN-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-1673: Attachment: YARN-1673-1.patch Fixing test. Thanks, Mayank Valid yarn kill application prints out help message. Key: YARN-1673 URL: https://issues.apache.org/jira/browse/YARN-1673 Project: Hadoop YARN Issue Type: Bug Components: client Affects Versions: 2.4.0 Reporter: Tassapol Athiapinya Assignee: Mayank Bansal Priority: Blocker Attachments: YARN-1673-1.patch, YARN-1673.patch, YARN-1673.txt yarn application -kill application ID used to work previously. In 2.4.0 it prints out help message and does not kill the application. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (YARN-1684) Fix history server heap size in yarn script
Billie Rinaldi created YARN-1684:
Summary: Fix history server heap size in yarn script
Key: YARN-1684
URL: https://issues.apache.org/jira/browse/YARN-1684
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Billie Rinaldi
The yarn script currently has the following:
{noformat}
if [ $YARN_RESOURCEMANAGER_HEAPSIZE != ]; then
JAVA_HEAP_MAX=-Xmx$YARN_HISTORYSERVER_HEAPSIZEm
fi
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1461) RM API and RM changes to handle tags for running jobs
[ https://issues.apache.org/jira/browse/YARN-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890086#comment-13890086 ] Zhijie Shen commented on YARN-1461: --- bq. However, I am curious why having two different enums, one in Java and one in proto, and a converter between the two is preferable to just having one enum and no converter? My understanding is that records.* wants to be decoupled with the PB implementation, while enum in proto is part of it. Then, users don't need to be aware of the PB implementation, and we can replace it wit other implementation if necessary. RM API and RM changes to handle tags for running jobs - Key: YARN-1461 URL: https://issues.apache.org/jira/browse/YARN-1461 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Affects Versions: 2.2.0 Reporter: Karthik Kambatla Assignee: Karthik Kambatla Attachments: yarn-1461-1.patch, yarn-1461-10.patch, yarn-1461-2.patch, yarn-1461-3.patch, yarn-1461-4.patch, yarn-1461-5.patch, yarn-1461-6.patch, yarn-1461-6.patch, yarn-1461-7.patch, yarn-1461-8.patch, yarn-1461-9.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1461) RM API and RM changes to handle tags for running jobs
[ https://issues.apache.org/jira/browse/YARN-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890090#comment-13890090 ] Zhijie Shen commented on YARN-1461: --- +1. LGTM RM API and RM changes to handle tags for running jobs - Key: YARN-1461 URL: https://issues.apache.org/jira/browse/YARN-1461 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Affects Versions: 2.2.0 Reporter: Karthik Kambatla Assignee: Karthik Kambatla Attachments: yarn-1461-1.patch, yarn-1461-10.patch, yarn-1461-2.patch, yarn-1461-3.patch, yarn-1461-4.patch, yarn-1461-5.patch, yarn-1461-6.patch, yarn-1461-6.patch, yarn-1461-7.patch, yarn-1461-8.patch, yarn-1461-9.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1461) RM API and RM changes to handle tags for running jobs
[ https://issues.apache.org/jira/browse/YARN-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890099#comment-13890099 ] Vinod Kumar Vavilapalli commented on YARN-1461: --- Let me quickly give a look at it.. RM API and RM changes to handle tags for running jobs - Key: YARN-1461 URL: https://issues.apache.org/jira/browse/YARN-1461 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Affects Versions: 2.2.0 Reporter: Karthik Kambatla Assignee: Karthik Kambatla Attachments: yarn-1461-1.patch, yarn-1461-10.patch, yarn-1461-2.patch, yarn-1461-3.patch, yarn-1461-4.patch, yarn-1461-5.patch, yarn-1461-6.patch, yarn-1461-6.patch, yarn-1461-7.patch, yarn-1461-8.patch, yarn-1461-9.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1497) Expose moving apps between queues on the command line
[ https://issues.apache.org/jira/browse/YARN-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1497: - Attachment: YARN-1497.patch Expose moving apps between queues on the command line - Key: YARN-1497 URL: https://issues.apache.org/jira/browse/YARN-1497 Project: Hadoop YARN Issue Type: Sub-task Components: client Affects Versions: 2.2.0 Reporter: Sandy Ryza Assignee: Sandy Ryza Attachments: YARN-1497.patch, YARN-1497.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (YARN-1684) Fix history server heap size in yarn script
[
https://issues.apache.org/jira/browse/YARN-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi reassigned YARN-1684:
Assignee: Billie Rinaldi
Fix history server heap size in yarn script
---
Key: YARN-1684
URL: https://issues.apache.org/jira/browse/YARN-1684
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Billie Rinaldi
Assignee: Billie Rinaldi
Attachments: YARN-1684.patch
The yarn script currently has the following:
{noformat}
if [ $YARN_RESOURCEMANAGER_HEAPSIZE != ]; then
JAVA_HEAP_MAX=-Xmx$YARN_HISTORYSERVER_HEAPSIZEm
fi
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1684) Fix history server heap size in yarn script
[
https://issues.apache.org/jira/browse/YARN-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi updated YARN-1684:
-
Attachment: YARN-1684.patch
Fix history server heap size in yarn script
---
Key: YARN-1684
URL: https://issues.apache.org/jira/browse/YARN-1684
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Billie Rinaldi
Attachments: YARN-1684.patch
The yarn script currently has the following:
{noformat}
if [ $YARN_RESOURCEMANAGER_HEAPSIZE != ]; then
JAVA_HEAP_MAX=-Xmx$YARN_HISTORYSERVER_HEAPSIZEm
fi
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1673) Valid yarn kill application prints out help message.
[ https://issues.apache.org/jira/browse/YARN-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890121#comment-13890121 ] Vinod Kumar Vavilapalli commented on YARN-1673: --- Patch looks good to me. +1. Will check it in if/when jenkins says okay. Valid yarn kill application prints out help message. Key: YARN-1673 URL: https://issues.apache.org/jira/browse/YARN-1673 Project: Hadoop YARN Issue Type: Bug Components: client Affects Versions: 2.4.0 Reporter: Tassapol Athiapinya Assignee: Mayank Bansal Priority: Blocker Attachments: YARN-1673-1.patch, YARN-1673.patch, YARN-1673.txt yarn application -kill application ID used to work previously. In 2.4.0 it prints out help message and does not kill the application. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1684) Fix history server heap size in yarn script
[
https://issues.apache.org/jira/browse/YARN-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-1684:
--
Affects Version/s: 2.4.0
Fix history server heap size in yarn script
---
Key: YARN-1684
URL: https://issues.apache.org/jira/browse/YARN-1684
Project: Hadoop YARN
Issue Type: Sub-task
Affects Versions: 2.4.0
Reporter: Billie Rinaldi
Assignee: Billie Rinaldi
Attachments: YARN-1684.patch
The yarn script currently has the following:
{noformat}
if [ $YARN_RESOURCEMANAGER_HEAPSIZE != ]; then
JAVA_HEAP_MAX=-Xmx$YARN_HISTORYSERVER_HEAPSIZEm
fi
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1684) Fix history server heap size in yarn script
[
https://issues.apache.org/jira/browse/YARN-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi updated YARN-1684:
-
Attachment: YARN-1684.2.patch
Fix history server heap size in yarn script
---
Key: YARN-1684
URL: https://issues.apache.org/jira/browse/YARN-1684
Project: Hadoop YARN
Issue Type: Sub-task
Affects Versions: 2.4.0
Reporter: Billie Rinaldi
Assignee: Billie Rinaldi
Attachments: YARN-1684.2.patch, YARN-1684.patch
The yarn script currently has the following:
{noformat}
if [ $YARN_RESOURCEMANAGER_HEAPSIZE != ]; then
JAVA_HEAP_MAX=-Xmx$YARN_HISTORYSERVER_HEAPSIZEm
fi
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1669) Make admin refreshServiceAcls work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1669: Attachment: YARN-1669.3.patch Make admin refreshServiceAcls work across RM failover - Key: YARN-1669 URL: https://issues.apache.org/jira/browse/YARN-1669 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Attachments: YARN-1669.1.patch, YARN-1669.2.patch, YARN-1669.3.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890163#comment-13890163 ] Vinod Kumar Vavilapalli commented on YARN-1637: --- This looks fine to me overall. +1 pending Jenkins. Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890172#comment-13890172 ] Sandy Ryza commented on YARN-1637: -- I'd like to take a quick look at this. Will do it today. Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1684) Fix history server heap size in yarn script
[
https://issues.apache.org/jira/browse/YARN-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890179#comment-13890179
]
Zhijie Shen commented on YARN-1684:
---
+1. LGTM. Wait for Jenkins before committing, though it should be trivial.
Fix history server heap size in yarn script
---
Key: YARN-1684
URL: https://issues.apache.org/jira/browse/YARN-1684
Project: Hadoop YARN
Issue Type: Sub-task
Affects Versions: 2.4.0
Reporter: Billie Rinaldi
Assignee: Billie Rinaldi
Attachments: YARN-1684.2.patch, YARN-1684.patch
The yarn script currently has the following:
{noformat}
if [ $YARN_RESOURCEMANAGER_HEAPSIZE != ]; then
JAVA_HEAP_MAX=-Xmx$YARN_HISTORYSERVER_HEAPSIZEm
fi
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890211#comment-13890211 ] Billie Rinaldi commented on YARN-1637: -- The YarnJacksonJaxbJsonProvider still has the comment about the deprecated methods (which has already been addressed in the patch), and it says mapper.setAnnotationIntrospector(introspector) twice in a row. Otherwise the patch looks good to me. Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1461) RM API and RM changes to handle tags for running jobs
[ https://issues.apache.org/jira/browse/YARN-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890209#comment-13890209 ] Vinod Kumar Vavilapalli commented on YARN-1461: --- Looks fine overall. Few comments: - Do you want to move the constants in ApplicationSubmissionContext - MAX_TAGS and MAX_TAG_LENGTH to YarnConfiguration? - Tags may take too much space on the app-list page. 10 of them definitely will. I think we should only show them on the per-app page. - Should we call them Application Tags everywhere instead of just tags. We call name, type etc like that, so.. - Add new APIs to GetApplicationsRequest which take in tags/scope as input? RM API and RM changes to handle tags for running jobs - Key: YARN-1461 URL: https://issues.apache.org/jira/browse/YARN-1461 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Affects Versions: 2.2.0 Reporter: Karthik Kambatla Assignee: Karthik Kambatla Attachments: yarn-1461-1.patch, yarn-1461-10.patch, yarn-1461-2.patch, yarn-1461-3.patch, yarn-1461-4.patch, yarn-1461-5.patch, yarn-1461-6.patch, yarn-1461-6.patch, yarn-1461-7.patch, yarn-1461-8.patch, yarn-1461-9.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1637: -- Attachment: YARN-1637.4.patch Good catch, Billie! Upload a new patch to address your comments. Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch, YARN-1637.4.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[
https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890224#comment-13890224
]
Sandy Ryza commented on YARN-1637:
--
What's the need for the PutErrors and Events classes? They appear to just wrap
list objects?
{code}
+ * The client library that can be used to post the information of a number of
+ * conceptual entities of an application.
{code}
This sounds a little clearer to me:
A client library that can be used to post information about an application's
{@link Entity}s to the Application Timeline Store.
TimelineClient sounds like it could refer to a lot of different things. Maybe
ApplicationTimelineClient or ApplicationTimelineStoreClient would be clearer?
Not hard on this one.
How does the client get access do the PutErrors? Or is it not supposed to and
I'm misunderstanding.
Implement a client library for java users to post entities+events
-
Key: YARN-1637
URL: https://issues.apache.org/jira/browse/YARN-1637
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Vinod Kumar Vavilapalli
Assignee: Zhijie Shen
Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch,
YARN-1637.4.patch
This is a wrapper around the web-service to facilitate easy posting of
entity+event data to the time-line server.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1553) Do not use HttpConfig.isSecure() in YARN
[
https://issues.apache.org/jira/browse/YARN-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890237#comment-13890237
]
Hadoop QA commented on YARN-1553:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626753/YARN-1553.003.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy:
org.apache.hadoop.mapreduce.v2.app.TestRMContainerAllocator
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2996//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/2996//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2996//console
This message is automatically generated.
Do not use HttpConfig.isSecure() in YARN
Key: YARN-1553
URL: https://issues.apache.org/jira/browse/YARN-1553
Project: Hadoop YARN
Issue Type: Bug
Reporter: Haohui Mai
Assignee: Haohui Mai
Attachments: YARN-1553.000.patch, YARN-1553.001.patch,
YARN-1553.002.patch, YARN-1553.003.patch
HDFS-5305 and related jira decide that each individual project will have
their own configuration on http policy. {{HttpConfig.isSecure}} is a global
static method which does not fit the design anymore. The same functionality
should be moved into the YARN code base.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890238#comment-13890238 ] Billie Rinaldi commented on YARN-1637: -- bq. How does the client get access do the PutErrors? Or is it not supposed to and I'm misunderstanding. Good point, I think the client postEntities method should return PutErrors. Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch, YARN-1637.4.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1669) Make admin refreshServiceAcls work across RM failover
[
https://issues.apache.org/jira/browse/YARN-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890242#comment-13890242
]
Hadoop QA commented on YARN-1669:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626784/YARN-1669.3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2999//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/2999//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2999//console
This message is automatically generated.
Make admin refreshServiceAcls work across RM failover
-
Key: YARN-1669
URL: https://issues.apache.org/jira/browse/YARN-1669
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Xuan Gong
Assignee: Xuan Gong
Attachments: YARN-1669.1.patch, YARN-1669.2.patch, YARN-1669.3.patch
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890250#comment-13890250 ] Billie Rinaldi commented on YARN-1637: -- bq. What's the need for the PutErrors and Events classes? They appear to just wrap list objects? I believe that the wrappers aren't needed for the current JSON serialization, but if we want to enable serializing the objects to XML, we'll need the wrappers. Do let me know if I'm mistaken. Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch, YARN-1637.4.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890254#comment-13890254 ] Sandy Ryza commented on YARN-1637: -- If that's the case, we should explain that in a comment. Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch, YARN-1637.4.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1553) Do not use HttpConfig.isSecure() in YARN
[
https://issues.apache.org/jira/browse/YARN-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai updated YARN-1553:
-
Attachment: YARN-1553.004.patch
This v4 patch fixes the warnings from findbugs.
Do not use HttpConfig.isSecure() in YARN
Key: YARN-1553
URL: https://issues.apache.org/jira/browse/YARN-1553
Project: Hadoop YARN
Issue Type: Bug
Reporter: Haohui Mai
Assignee: Haohui Mai
Attachments: YARN-1553.000.patch, YARN-1553.001.patch,
YARN-1553.002.patch, YARN-1553.003.patch, YARN-1553.004.patch
HDFS-5305 and related jira decide that each individual project will have
their own configuration on http policy. {{HttpConfig.isSecure}} is a global
static method which does not fit the design anymore. The same functionality
should be moved into the YARN code base.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1499) Fair Scheduler changes for moving apps between queues
[ https://issues.apache.org/jira/browse/YARN-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890257#comment-13890257 ] Karthik Kambatla commented on YARN-1499: The patch mostly looks good to me. Minor comments: # FairScheduler#findLeastCommonAncestorQueue - can we rename this to make it clearer - lowestCommonAncestor or firstCommonAncestor. Should update the variable also accordingly. # FairScheduler#findLeastCommonAncestorQueue - I am not particular about this, but iterating through parents of one queue and checking if the other queue has this parent as part of its name might be easier to understand. # Few lines in the patch are longer than 80 chars. # FairScheduler#executeMove - we should make either make this synchronized or clearly document that the caller should hold a lock on FairScheduler Fair Scheduler changes for moving apps between queues - Key: YARN-1499 URL: https://issues.apache.org/jira/browse/YARN-1499 Project: Hadoop YARN Issue Type: Sub-task Components: scheduler Reporter: Sandy Ryza Assignee: Sandy Ryza Attachments: YARN-1499-1.patch, YARN-1499.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890258#comment-13890258 ] Vinod Kumar Vavilapalli commented on YARN-1637: --- bq. TimelineClient sounds like it could refer to a lot of different things. Maybe ApplicationTimelineClient or ApplicationTimelineStoreClient would be clearer? We want this client to be used beyond just applications. Like I mentioned in the design doc, ecosystem projects can also chose to write events that can be correlated with the resulting YARN/MR apps. Let's keep it TimelineClient due to that. Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch, YARN-1637.4.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890261#comment-13890261 ] Sandy Ryza commented on YARN-1637: -- bq. Like I mentioned in the design doc, ecosystem projects can also chose to write events that can be correlated with the resulting YARN/MR apps Makes sense. We should update naming in other places then, right? E.g. should the package name be apptimeline? Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch, YARN-1637.4.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1673) Valid yarn kill application prints out help message.
[
https://issues.apache.org/jira/browse/YARN-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890265#comment-13890265
]
Hadoop QA commented on YARN-1673:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626765/YARN-1673-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3001//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3001//console
This message is automatically generated.
Valid yarn kill application prints out help message.
Key: YARN-1673
URL: https://issues.apache.org/jira/browse/YARN-1673
Project: Hadoop YARN
Issue Type: Bug
Components: client
Affects Versions: 2.4.0
Reporter: Tassapol Athiapinya
Assignee: Mayank Bansal
Priority: Blocker
Attachments: YARN-1673-1.patch, YARN-1673.patch, YARN-1673.txt
yarn application -kill application ID
used to work previously. In 2.4.0 it prints out help message and does not
kill the application.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[
https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890266#comment-13890266
]
Hadoop QA commented on YARN-1637:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626794/YARN-1637.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 1556 javac
compiler warnings (more than the trunk's current 1545 warnings).
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3000//testReport/
Javac warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/3000//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3000//console
This message is automatically generated.
Implement a client library for java users to post entities+events
-
Key: YARN-1637
URL: https://issues.apache.org/jira/browse/YARN-1637
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Vinod Kumar Vavilapalli
Assignee: Zhijie Shen
Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch,
YARN-1637.4.patch
This is a wrapper around the web-service to facilitate easy posting of
entity+event data to the time-line server.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1497) Expose moving apps between queues on the command line
[
https://issues.apache.org/jira/browse/YARN-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890277#comment-13890277
]
Hadoop QA commented on YARN-1497:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626776/YARN-1497.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client:
org.apache.hadoop.yarn.client.cli.TestYarnCLI
The following test timeouts occurred in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client:
org.apache.hadoop.yarn.client.api.impl.TestNMClient
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2998//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2998//console
This message is automatically generated.
Expose moving apps between queues on the command line
-
Key: YARN-1497
URL: https://issues.apache.org/jira/browse/YARN-1497
Project: Hadoop YARN
Issue Type: Sub-task
Components: client
Affects Versions: 2.2.0
Reporter: Sandy Ryza
Assignee: Sandy Ryza
Attachments: YARN-1497.patch, YARN-1497.patch
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1684) Fix history server heap size in yarn script
[
https://issues.apache.org/jira/browse/YARN-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890289#comment-13890289
]
Hadoop QA commented on YARN-1684:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626781/YARN-1684.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3002//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3002//console
This message is automatically generated.
Fix history server heap size in yarn script
---
Key: YARN-1684
URL: https://issues.apache.org/jira/browse/YARN-1684
Project: Hadoop YARN
Issue Type: Sub-task
Affects Versions: 2.4.0
Reporter: Billie Rinaldi
Assignee: Billie Rinaldi
Attachments: YARN-1684.2.patch, YARN-1684.patch
The yarn script currently has the following:
{noformat}
if [ $YARN_RESOURCEMANAGER_HEAPSIZE != ]; then
JAVA_HEAP_MAX=-Xmx$YARN_HISTORYSERVER_HEAPSIZEm
fi
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1673) Valid yarn kill application prints out help message.
[ https://issues.apache.org/jira/browse/YARN-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890350#comment-13890350 ] Vinod Kumar Vavilapalli commented on YARN-1673: --- The javadoc warning is totally unrelated and in Common, will file a ticket. Checking this in. Valid yarn kill application prints out help message. Key: YARN-1673 URL: https://issues.apache.org/jira/browse/YARN-1673 Project: Hadoop YARN Issue Type: Bug Components: client Affects Versions: 2.4.0 Reporter: Tassapol Athiapinya Assignee: Mayank Bansal Priority: Blocker Attachments: YARN-1673-1.patch, YARN-1673.patch, YARN-1673.txt yarn application -kill application ID used to work previously. In 2.4.0 it prints out help message and does not kill the application. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1637) Implement a client library for java users to post entities+events
[ https://issues.apache.org/jira/browse/YARN-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890351#comment-13890351 ] Zhijie Shen commented on YARN-1637: --- [~sandyr], thanks for your review. bq. What's the need for the PutErrors and Events classes? They appear to just wrap list objects? It's needed because there should be something that works as the root element of XML content. We did something similar before, such as AppsInfo. However, in the early version, we may just support JSON content by making use of JacksonJaxbJsonProvider, it may be fine to remove them now, if you oppose the wrappers. Anyway, we should expect the POJO classes may involve with supporting XML content as well. It remind me that PutErrors gets annotated, and it's supposed to be return to the client to show the error of posting each individual entity. The client needs to be updated. Cancel the patch. Implement a client library for java users to post entities+events - Key: YARN-1637 URL: https://issues.apache.org/jira/browse/YARN-1637 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Zhijie Shen Attachments: YARN-1637.1.patch, YARN-1637.2.patch, YARN-1637.3.patch, YARN-1637.4.patch This is a wrapper around the web-service to facilitate easy posting of entity+event data to the time-line server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1285) Inconsistency of default yarn.acl.enable value
[ https://issues.apache.org/jira/browse/YARN-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890363#comment-13890363 ] Vinod Kumar Vavilapalli commented on YARN-1285: --- MAPREDUCE-3903 uncovered some major problems with ACLs (long time back), but seems like we didn't fix them in the ideal way possible. IAC, those are orthogonal issues and this patch is only fixing the inconsistency between code/documentation and the config files. +1, checking this in. Inconsistency of default yarn.acl.enable value Key: YARN-1285 URL: https://issues.apache.org/jira/browse/YARN-1285 Project: Hadoop YARN Issue Type: Bug Affects Versions: 2.2.0 Reporter: Zhijie Shen Assignee: Kenji Kikushima Attachments: YARN-1285.patch In yarn-default.xml, yarn.acl.enable is true while in YarnConfiguration, DEFAULT_YARN_ACL_ENABLE is false. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1285) Inconsistency of default yarn.acl.enable value
[ https://issues.apache.org/jira/browse/YARN-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890368#comment-13890368 ] Hudson commented on YARN-1285: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5101 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5101/]) YARN-1285. Changed the default value of yarn.acl.enable in yarn-default.xml to be consistent with what exists (false) in the code and documentation. Contributed by Kenji Kikushima. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564190) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml Inconsistency of default yarn.acl.enable value Key: YARN-1285 URL: https://issues.apache.org/jira/browse/YARN-1285 Project: Hadoop YARN Issue Type: Bug Affects Versions: 2.2.0 Reporter: Zhijie Shen Assignee: Kenji Kikushima Fix For: 2.4.0 Attachments: YARN-1285.patch In yarn-default.xml, yarn.acl.enable is true while in YarnConfiguration, DEFAULT_YARN_ACL_ENABLE is false. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-967) [YARN-321] Command Line Interface(CLI) for Reading Application History Storage Data
[ https://issues.apache.org/jira/browse/YARN-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890366#comment-13890366 ] Hudson commented on YARN-967: - SUCCESS: Integrated in Hadoop-trunk-Commit #5101 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5101/]) YARN-1673. Fix option parsing in YARN's application CLI after it is broken by YARN-967. Contributed by Mayank Bansal. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564188) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ApplicationCLI.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestYarnCLI.java [YARN-321] Command Line Interface(CLI) for Reading Application History Storage Data --- Key: YARN-967 URL: https://issues.apache.org/jira/browse/YARN-967 Project: Hadoop YARN Issue Type: Sub-task Reporter: Devaraj K Assignee: Mayank Bansal Fix For: 2.4.0 Attachments: YARN-967-1.patch, YARN-967-10.patch, YARN-967-11.patch, YARN-967-12.patch, YARN-967-13.patch, YARN-967-14.patch, YARN-967-2.patch, YARN-967-3.patch, YARN-967-4.patch, YARN-967-5.patch, YARN-967-6.patch, YARN-967-7.patch, YARN-967-8.patch, YARN-967-9.patch, YARN-967.15.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1667) Make admin refreshSuperUserGroupsConfiguration work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890367#comment-13890367 ] Hudson commented on YARN-1667: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5101 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5101/]) Fix YARN's CHANGES.txt issue caused during the commit for YARN-1667. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564185) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt Make admin refreshSuperUserGroupsConfiguration work across RM failover -- Key: YARN-1667 URL: https://issues.apache.org/jira/browse/YARN-1667 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Fix For: 2.4.0 Attachments: YARN-1667.1.patch, YARN-1667.2.patch, YARN-1667.3.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1673) Valid yarn kill application prints out help message.
[ https://issues.apache.org/jira/browse/YARN-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890365#comment-13890365 ] Hudson commented on YARN-1673: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5101 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5101/]) YARN-1673. Fix option parsing in YARN's application CLI after it is broken by YARN-967. Contributed by Mayank Bansal. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564188) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ApplicationCLI.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestYarnCLI.java Valid yarn kill application prints out help message. Key: YARN-1673 URL: https://issues.apache.org/jira/browse/YARN-1673 Project: Hadoop YARN Issue Type: Bug Components: client Affects Versions: 2.4.0 Reporter: Tassapol Athiapinya Assignee: Mayank Bansal Priority: Blocker Fix For: 2.4.0 Attachments: YARN-1673-1.patch, YARN-1673.patch, YARN-1673.txt yarn application -kill application ID used to work previously. In 2.4.0 it prints out help message and does not kill the application. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1684) Fix history server heap size in yarn script
[
https://issues.apache.org/jira/browse/YARN-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890377#comment-13890377
]
Zhijie Shen commented on YARN-1684:
---
The javadoc warnings are unrelated.
Committed to trunk and branch-2. Thanks, [~billie.rinaldi]!
Fix history server heap size in yarn script
---
Key: YARN-1684
URL: https://issues.apache.org/jira/browse/YARN-1684
Project: Hadoop YARN
Issue Type: Sub-task
Affects Versions: 2.4.0
Reporter: Billie Rinaldi
Assignee: Billie Rinaldi
Fix For: 2.4.0
Attachments: YARN-1684.2.patch, YARN-1684.patch
The yarn script currently has the following:
{noformat}
if [ $YARN_RESOURCEMANAGER_HEAPSIZE != ]; then
JAVA_HEAP_MAX=-Xmx$YARN_HISTORYSERVER_HEAPSIZEm
fi
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1553) Do not use HttpConfig.isSecure() in YARN
[
https://issues.apache.org/jira/browse/YARN-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890384#comment-13890384
]
Hadoop QA commented on YARN-1553:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626804/YARN-1553.004.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy:
org.apache.hadoop.mapreduce.v2.app.TestRMContainerAllocator
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3003//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3003//console
This message is automatically generated.
Do not use HttpConfig.isSecure() in YARN
Key: YARN-1553
URL: https://issues.apache.org/jira/browse/YARN-1553
Project: Hadoop YARN
Issue Type: Bug
Reporter: Haohui Mai
Assignee: Haohui Mai
Attachments: YARN-1553.000.patch, YARN-1553.001.patch,
YARN-1553.002.patch, YARN-1553.003.patch, YARN-1553.004.patch
HDFS-5305 and related jira decide that each individual project will have
their own configuration on http policy. {{HttpConfig.isSecure}} is a global
static method which does not fit the design anymore. The same functionality
should be moved into the YARN code base.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1669) Make admin refreshServiceAcls work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1669: Attachment: YARN-1669.4.patch Make admin refreshServiceAcls work across RM failover - Key: YARN-1669 URL: https://issues.apache.org/jira/browse/YARN-1669 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Attachments: YARN-1669.1.patch, YARN-1669.2.patch, YARN-1669.3.patch, YARN-1669.4.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1684) Fix history server heap size in yarn script
[
https://issues.apache.org/jira/browse/YARN-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890389#comment-13890389
]
Hudson commented on YARN-1684:
--
SUCCESS: Integrated in Hadoop-trunk-Commit #5102 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5102/])
YARN-1684. Fixed history server heap size in yarn script. Contributed by Billie
Rinaldi. (zjshen:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1564193)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/bin/yarn
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd
Fix history server heap size in yarn script
---
Key: YARN-1684
URL: https://issues.apache.org/jira/browse/YARN-1684
Project: Hadoop YARN
Issue Type: Sub-task
Affects Versions: 2.4.0
Reporter: Billie Rinaldi
Assignee: Billie Rinaldi
Fix For: 2.4.0
Attachments: YARN-1684.2.patch, YARN-1684.patch
The yarn script currently has the following:
{noformat}
if [ $YARN_RESOURCEMANAGER_HEAPSIZE != ]; then
JAVA_HEAP_MAX=-Xmx$YARN_HISTORYSERVER_HEAPSIZEm
fi
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1669) Make admin refreshServiceAcls work across RM failover
[
https://issues.apache.org/jira/browse/YARN-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890430#comment-13890430
]
Hadoop QA commented on YARN-1669:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626829/YARN-1669.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3004//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3004//console
This message is automatically generated.
Make admin refreshServiceAcls work across RM failover
-
Key: YARN-1669
URL: https://issues.apache.org/jira/browse/YARN-1669
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Xuan Gong
Assignee: Xuan Gong
Attachments: YARN-1669.1.patch, YARN-1669.2.patch, YARN-1669.3.patch,
YARN-1669.4.patch
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1669) Make admin refreshServiceAcls work across RM failover
[ https://issues.apache.org/jira/browse/YARN-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890439#comment-13890439 ] Xuan Gong commented on YARN-1669: - javadoc warning messages are un-related Make admin refreshServiceAcls work across RM failover - Key: YARN-1669 URL: https://issues.apache.org/jira/browse/YARN-1669 Project: Hadoop YARN Issue Type: Sub-task Reporter: Xuan Gong Assignee: Xuan Gong Attachments: YARN-1669.1.patch, YARN-1669.2.patch, YARN-1669.3.patch, YARN-1669.4.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1542) Add unit test for public resource on viewfs
[ https://issues.apache.org/jira/browse/YARN-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gera Shegalov updated YARN-1542: Attachment: YARN-1542.v02.patch v02 restoring permissions on after the test end Add unit test for public resource on viewfs --- Key: YARN-1542 URL: https://issues.apache.org/jira/browse/YARN-1542 Project: Hadoop YARN Issue Type: Improvement Components: nodemanager Reporter: Gera Shegalov Assignee: Gera Shegalov Attachments: YARN-1542.v01.patch, YARN-1542.v02.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1461) RM API and RM changes to handle tags for running jobs
[ https://issues.apache.org/jira/browse/YARN-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1461: --- Attachment: yarn-1461-11.patch RM API and RM changes to handle tags for running jobs - Key: YARN-1461 URL: https://issues.apache.org/jira/browse/YARN-1461 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Affects Versions: 2.2.0 Reporter: Karthik Kambatla Assignee: Karthik Kambatla Attachments: yarn-1461-1.patch, yarn-1461-10.patch, yarn-1461-11.patch, yarn-1461-2.patch, yarn-1461-3.patch, yarn-1461-4.patch, yarn-1461-5.patch, yarn-1461-6.patch, yarn-1461-6.patch, yarn-1461-7.patch, yarn-1461-8.patch, yarn-1461-9.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1461) RM API and RM changes to handle tags for running jobs
[ https://issues.apache.org/jira/browse/YARN-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1461: --- Attachment: yarn-1461-11.patch RM API and RM changes to handle tags for running jobs - Key: YARN-1461 URL: https://issues.apache.org/jira/browse/YARN-1461 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Affects Versions: 2.2.0 Reporter: Karthik Kambatla Assignee: Karthik Kambatla Attachments: yarn-1461-1.patch, yarn-1461-10.patch, yarn-1461-11.patch, yarn-1461-2.patch, yarn-1461-3.patch, yarn-1461-4.patch, yarn-1461-5.patch, yarn-1461-6.patch, yarn-1461-6.patch, yarn-1461-7.patch, yarn-1461-8.patch, yarn-1461-9.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1542) Add unit test for public resource on viewfs
[
https://issues.apache.org/jira/browse/YARN-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890475#comment-13890475
]
Hadoop QA commented on YARN-1542:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626837/YARN-1542.v02.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:
org.apache.hadoop.yarn.util.TestFSDownload
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3006//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3006//console
This message is automatically generated.
Add unit test for public resource on viewfs
---
Key: YARN-1542
URL: https://issues.apache.org/jira/browse/YARN-1542
Project: Hadoop YARN
Issue Type: Improvement
Components: nodemanager
Reporter: Gera Shegalov
Assignee: Gera Shegalov
Attachments: YARN-1542.v01.patch, YARN-1542.v02.patch
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1461) RM API and RM changes to handle tags for running jobs
[ https://issues.apache.org/jira/browse/YARN-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890476#comment-13890476 ] Vinod Kumar Vavilapalli commented on YARN-1461: --- The GetApplicationsRequest API should take either/or or both tags/scope as input? RM API and RM changes to handle tags for running jobs - Key: YARN-1461 URL: https://issues.apache.org/jira/browse/YARN-1461 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Affects Versions: 2.2.0 Reporter: Karthik Kambatla Assignee: Karthik Kambatla Attachments: yarn-1461-1.patch, yarn-1461-10.patch, yarn-1461-11.patch, yarn-1461-2.patch, yarn-1461-3.patch, yarn-1461-4.patch, yarn-1461-5.patch, yarn-1461-6.patch, yarn-1461-6.patch, yarn-1461-7.patch, yarn-1461-8.patch, yarn-1461-9.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
