[ 
https://issues.apache.org/jira/browse/AMBARI-12114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599530#comment-14599530
 ] 

Srimanth Gunturi commented on AMBARI-12114:
-------------------------------------------

For this fix I had to undo the changes made by AMBARI-11700 and tolerate 
non-HDP stacks. As requested by AMBARI-11700, the 
{{YarnTimelineServerStatePreservingCheck}} check is now applicable for any 
non-HDP stacks. It is _not applicable_ only for HDP stacks lesser than 
HDP-2.2.4.2.

Changes were made only for _SERVICES_YARN_TIMELINE_ST, 
SERVICES_HIVE_DYNAMIC_SERVICE_DISCOVERY_ and _SERVICES_NAMENODE_TRUNCATE_. New 
tests were added for the changes.

Awaiting review by committers and also added [~dili] to review the changes.

> RU: prereqs need to be upgrade pack specific
> --------------------------------------------
>
>                 Key: AMBARI-12114
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12114
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12114.patch
>
>
> The table below lists the *new* checks as of Ambari 2.1.0 and columns for 
> upgrade paths where the check is applicable...
> ||Check|| HDP 2.2.x -> 2.2.y || HDP 2.2.x -> 2.3.x || HDP 2.3.x -> 2.3.y ||
> | SERVICES_YARN_TIMELINE_ST / if (yarn.timeline-service.recovery.enabled) 
> what to do? | FAIL, only if starting at 2.2.4.2 or later | FAIL, only if 
> starting at 2.2.4.2 or later | FAIL |
> | SERVICES_HIVE_DYNAMIC_SERVICE_DISCOVERY| WARN | FAIL | FAIL |
> | SERVICES_MR_DISTRIBUTED_CACHE | FAIL | FAIL | FAIL |
> | SERVICES_NAMENODE_TRUNCATE / if (dfs.allow.truncate) what to do? | FAIL | 
> FAIL | ALLOW |
> | SERVICES_TEZ_DISTRIBUTED_CACHE | FAIL | FAIL | FAIL |



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

Reply via email to