hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore
Date Thu, 18 Sep 2014 23:45:35 GMT

    [ 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)

Mime
View raw message