hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1749) Review AHS configs and sycn them up with the timeline-service configs
Date Sat, 22 Feb 2014 21:37:20 GMT

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

Zhijie Shen updated YARN-1749:

    Attachment: YARN-1749.4.patch

bq. We've gotten rid of history-writer.* in YarnConfiguration, but yarn-default.xml is not
yet updated regarding the same.

Removed in yarn-default.xml as well, and move app-history.enable to timeline config section.

bq. We still have history-writer.multi-threaded-dispatcher.pool-size. Which seems fine, but
let me know what you think.

Yes, we should have it as it reflect a writer class in RM

bq. Let's mark all the configs related to app-history as @Private for now. As we merge generic
history with the timeline-service, some of it will change.

Done with adding the comment as well

> 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, YARN-1749.4.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

This message was sent by Atlassian JIRA

View raw message