[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
[ https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142067#comment-14142067 ] Hudson commented on YARN-2565: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1902 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1902/]) YARN-2565. Fixed RM to not use FileSystemApplicationHistoryStore unless explicitly set. Contributed by Zhijie Shen (jianhe: rev 444acf8ea795e4bc782f1ce3b5ef7a1a47d1d27d) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ahs/RMApplicationHistoryWriter.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/ahs/TestRMApplicationHistoryWriter.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/ApplicationHistoryServer.java > RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting > FileSystemApplicationHistoryStore > --- > > Key: YARN-2565 > URL: https://issues.apache.org/jira/browse/YARN-2565 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, timelineserver >Affects Versions: 2.6.0 > Environment: Secure cluster with ATS (timeline server enabled) and > yarn.resourcemanager.system-metrics-publisher.enabled=true > so that RM can send Application history to Timeline Store >Reporter: Karam Singh >Assignee: Zhijie Shen > Fix For: 2.6.0 > > Attachments: YARN-2565.1.patch, YARN-2565.2.patch, YARN-2565.3.patch > > > Observed that RM fails to start in Secure mode when GenericeHistoryService is > enabled and ResourceManager is set to use Timeline Store -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
[ https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141973#comment-14141973 ] Hudson commented on YARN-2565: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1877 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1877/]) YARN-2565. Fixed RM to not use FileSystemApplicationHistoryStore unless explicitly set. Contributed by Zhijie Shen (jianhe: rev 444acf8ea795e4bc782f1ce3b5ef7a1a47d1d27d) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ahs/RMApplicationHistoryWriter.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/ApplicationHistoryServer.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/ahs/TestRMApplicationHistoryWriter.java > RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting > FileSystemApplicationHistoryStore > --- > > Key: YARN-2565 > URL: https://issues.apache.org/jira/browse/YARN-2565 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, timelineserver >Affects Versions: 2.6.0 > Environment: Secure cluster with ATS (timeline server enabled) and > yarn.resourcemanager.system-metrics-publisher.enabled=true > so that RM can send Application history to Timeline Store >Reporter: Karam Singh >Assignee: Zhijie Shen > Fix For: 2.6.0 > > Attachments: YARN-2565.1.patch, YARN-2565.2.patch, YARN-2565.3.patch > > > Observed that RM fails to start in Secure mode when GenericeHistoryService is > enabled and ResourceManager is set to use Timeline Store -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
[ https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141931#comment-14141931 ] Hudson commented on YARN-2565: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #686 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/686/]) YARN-2565. Fixed RM to not use FileSystemApplicationHistoryStore unless explicitly set. Contributed by Zhijie Shen (jianhe: rev 444acf8ea795e4bc782f1ce3b5ef7a1a47d1d27d) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ahs/RMApplicationHistoryWriter.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/ahs/TestRMApplicationHistoryWriter.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/ApplicationHistoryServer.java > RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting > FileSystemApplicationHistoryStore > --- > > Key: YARN-2565 > URL: https://issues.apache.org/jira/browse/YARN-2565 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, timelineserver >Affects Versions: 2.6.0 > Environment: Secure cluster with ATS (timeline server enabled) and > yarn.resourcemanager.system-metrics-publisher.enabled=true > so that RM can send Application history to Timeline Store >Reporter: Karam Singh >Assignee: Zhijie Shen > Fix For: 2.6.0 > > Attachments: YARN-2565.1.patch, YARN-2565.2.patch, YARN-2565.3.patch > > > Observed that RM fails to start in Secure mode when GenericeHistoryService is > enabled and ResourceManager is set to use Timeline Store -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
[ https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141024#comment-14141024 ] Jian He commented on YARN-2565: --- looks good, committing > RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting > FileSystemApplicationHistoryStore > --- > > Key: YARN-2565 > URL: https://issues.apache.org/jira/browse/YARN-2565 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, timelineserver >Affects Versions: 2.6.0 > Environment: Secure cluster with ATS (timeline server enabled) and > yarn.resourcemanager.system-metrics-publisher.enabled=true > so that RM can send Application history to Timeline Store >Reporter: Karam Singh >Assignee: Zhijie Shen > Attachments: YARN-2565.1.patch, YARN-2565.2.patch, YARN-2565.3.patch > > > Observed that RM fails to start in Secure mode when GenericeHistoryService is > enabled and ResourceManager is set to use Timeline Store -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
[
https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139873#comment-14139873
]
Hadoop QA commented on YARN-2565:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12669873/YARN-2565.3.patch
against trunk revision 6434572.
{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}. There were no new javadoc 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 2.0.3) 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-applicationhistoryservice
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/5035//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5035//console
This message is automatically generated.
> RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting
> FileSystemApplicationHistoryStore
> ---
>
> Key: YARN-2565
> URL: https://issues.apache.org/jira/browse/YARN-2565
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, timelineserver
>Affects Versions: 2.6.0
> Environment: Secure cluster with ATS (timeline server enabled) and
> yarn.resourcemanager.system-metrics-publisher.enabled=true
> so that RM can send Application history to Timeline Store
>Reporter: Karam Singh
>Assignee: Zhijie Shen
> Attachments: YARN-2565.1.patch, YARN-2565.2.patch, YARN-2565.3.patch
>
>
> Observed that RM fails to start in Secure mode when GenericeHistoryService is
> enabled and ResourceManager is set to use Timeline Store
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
[
https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139817#comment-14139817
]
Hadoop QA commented on YARN-2565:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12669873/YARN-2565.3.patch
against trunk revision 20a076b.
{color:red}-1 @author{color}. The patch appears to contain @author tags
which the Hadoop community has agreed to not allow in code contributions.
{color:green}+1 tests included{color}. The patch appears to include new
or modified test files.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5034//console
This message is automatically generated.
> RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting
> FileSystemApplicationHistoryStore
> ---
>
> Key: YARN-2565
> URL: https://issues.apache.org/jira/browse/YARN-2565
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, timelineserver
>Affects Versions: 2.6.0
> Environment: Secure cluster with ATS (timeline server enabled) and
> yarn.resourcemanager.system-metrics-publisher.enabled=true
> so that RM can send Application history to Timeline Store
>Reporter: Karam Singh
>Assignee: Zhijie Shen
> Attachments: YARN-2565.1.patch, YARN-2565.2.patch, YARN-2565.3.patch
>
>
> Observed that RM fails to start in Secure mode when GenericeHistoryService is
> enabled and ResourceManager is set to use Timeline Store
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
[
https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139746#comment-14139746
]
Jian He commented on YARN-2565:
---
- exception msg seems still using FileSystemApplicationHistoryStore
{code}
"Could not instantiate ApplicationHistoryWriter: "
+ conf.get(YarnConfiguration.APPLICATION_HISTORY_STORE,
FileSystemApplicationHistoryStore.class.getName());
{code}
- testDefaultStoreSetup: missing @test annotation
> RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting
> FileSystemApplicationHistoryStore
> ---
>
> Key: YARN-2565
> URL: https://issues.apache.org/jira/browse/YARN-2565
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, timelineserver
>Affects Versions: 2.6.0
> Environment: Secure cluster with ATS (timeline server enabled) and
> yarn.resourcemanager.system-metrics-publisher.enabled=true
> so that RM can send Application history to Timeline Store
>Reporter: Karam Singh
>Assignee: Zhijie Shen
> Attachments: YARN-2565.1.patch, YARN-2565.2.patch
>
>
> Observed that RM fails to start in Secure mode when GenericeHistoryService is
> enabled and ResourceManager is set to use Timeline Store
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
[
https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138369#comment-14138369
]
Hadoop QA commented on YARN-2565:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12669577/YARN-2565.2.patch
against trunk revision 123f20d.
{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}. There were no new javadoc 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 2.0.3) 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-applicationhistoryservice
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/5014//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5014//console
This message is automatically generated.
> RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting
> FileSystemApplicationHistoryStore
> ---
>
> Key: YARN-2565
> URL: https://issues.apache.org/jira/browse/YARN-2565
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, timelineserver
>Affects Versions: 2.6.0
> Environment: Secure cluster with ATS (timeline server enabled) and
> yarn.resourcemanager.system-metrics-publisher.enabled=true
> so that RM can send Application history to Timeline Store
>Reporter: Karam Singh
>Assignee: Zhijie Shen
> Attachments: YARN-2565.1.patch, YARN-2565.2.patch
>
>
> Observed that RM fails to start in Secure mode when GenericeHistoryService is
> enabled and ResourceManager is set to use Timeline Store
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
[
https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138232#comment-14138232
]
Hadoop QA commented on YARN-2565:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12669564/YARN-2565.1.patch
against trunk revision 123f20d.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5010//console
This message is automatically generated.
> RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting
> FileSystemApplicationHistoryStore
> ---
>
> Key: YARN-2565
> URL: https://issues.apache.org/jira/browse/YARN-2565
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, timelineserver
>Affects Versions: 2.6.0
> Environment: Secure cluster with ATS (timeline server enabled) and
> yarn.resourcemanager.system-metrics-publisher.enabled=true
> so that RM can send Application history to Timeline Store
>Reporter: Karam Singh
>Assignee: Zhijie Shen
> Attachments: YARN-2565.1.patch
>
>
> Observed that RM fails to start in Secure mode when GenericeHistoryService is
> enabled and ResourceManager is set to use Timeline Store
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
