You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2014/02/22 22:17:21 UTC

[jira] [Updated] (YARN-1749) Review AHS configs and sycn them up with the timeline-service configs

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

Vinod Kumar Vavilapalli updated YARN-1749:
------------------------------------------

    Summary: Review AHS configs and sycn them up with the timeline-service configs  (was: Misc fixes of AHS configurations and related behavior)

> Review AHS configs and sycn them up with the timeline-service configs
> ---------------------------------------------------------------------
>
>                 Key: YARN-1749
>                 URL: https://issues.apache.org/jira/browse/YARN-1749
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>         Attachments: YARN-1687+YARN-1732+YARN-1749.1.patch, YARN-1687+YARN-1732+YARN-1749.2.patch, YARN-1749.1.patch, YARN-1749.2.patch, YARN-1749.3.patch
>
>
> We need to:
> 1. Review the configuration names and default values
> 2. Combine the two store class configurations
> Some other thoughts:
> 1. Maybe we don't need null implementation of ApplicationHistoryStore any more
> 2. Maybe if yarn.ahs.enabled = false, we should stop AHS web server returning historic information



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)