ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-14056) Stack Upgrade from HDP 2.1 or 2.2 to 2.3 to preserve configs for AppTimelineServer ATS version 1.0
Date Wed, 25 Nov 2015 01:24:12 GMT

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

Alejandro Fernandez updated AMBARI-14056:
-----------------------------------------
    Affects Version/s: Ambari-2.1.3

> Stack Upgrade from HDP 2.1 or 2.2 to 2.3 to preserve configs for AppTimelineServer ATS
version 1.0
> --------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14056
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14056
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.3
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Critical
>             Fix For: 2.2.0, 2.1.3
>
>
> HDP 2.3.4.0 has support for both AppTimelineServer v1.0 and v1.5
> The HDP 2.3 stack definition will make ATS v1.5 the default for configs.
> This means that any stack upgrade that modifies the configs and upgrades to version x
where 2.3.0.0 <= x < 2.3.4.0 will fail since those binaries only support ATS v1.0 but
the configs are for ATS 1.5.
> The fix is to modify the following upgrade packs
> HDP 2.1 -> 2.3 in nonrolling
> HDP 2.2 -> 2.3 in both rolling and nonrolling
> So that they preserve the ATS v1.0 configs.
> For tez-site, keep
> {code}
> tez.history.logging.service.class = org.apache.tez.dag.history.logging.ats.ATSHistoryLoggingService
> {code}
> For yarn-site, keep 
> {code}
> yarn.timeline-service.version = 1.0
> yarn.timeline-service.store-class = org.apache.hadoop.yarn.server.timeline.LeveldbTimelineStore
> {code}
> and it's ok to add the HDP 2.3 configs that are not being used, e.g.,
> {code}
> yarn.timeline-service.entity-group-fs-store.group-id-plugin-classes = org.apache.tez.dag.history.logging.ats.TimelineCachePluginImpl
> yarn.timeline-service.entity-group-fs-store.summary-store = org.apache.hadoop.yarn.server.timeline.RollingLevelDBTimelineStore
> yarn.timeline-service.entity-group-fs-store.scan-interval-seconds = 60
> yarn.timeline-service.entity-group-fs-store.cleaner-interval-seconds = 3600
> yarn.timeline-service.entity-group-fs-store.retain-seconds = 604800
> yarn.timeline-service.entity-group-fs-store.active-dir = /ats/active/
> yarn.timeline-service.entity-group-fs-store.done-dir = /ats/done/
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message