You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2015/11/12 20:57:11 UTC
[jira] [Resolved] (AMBARI-13845) Breakout Some Service Masters Into
Their Own Groups To Prevent Auto Skip On Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-13845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley resolved AMBARI-13845.
--------------------------------------
Resolution: Fixed
> Breakout Some Service Masters Into Their Own Groups To Prevent Auto Skip On Upgrade
> -----------------------------------------------------------------------------------
>
> Key: AMBARI-13845
> URL: https://issues.apache.org/jira/browse/AMBARI-13845
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.3
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.1.3
>
>
> The ability to automatically skip failures on skippable components is being expanded to master components incorrectly. This is because those non-core masters are considered to be skippable in general.
> The best way to fix this is to adjust the upgrade packs to break out the master components into their own groupings which can be annotated with
> {code}
> <skippable>true</skippable>
> <supports-auto-skip-failure>false</supports-auto-skip-failure>
> {code}
> This will apply to:
> - Ranger
> - Spark
> - Oozie
> - Falcon
> {code:title=Example}
> <group name="SPARK" title="Spark">
> <skippable>true</skippable>
> <service-check>false</service-check>
> <supports-auto-skip>false</supports-auto-skip>
> <service name="SPARK">
> <component>SPARK_JOBHISTORYSERVER</component>
> </service>
> </group>
> <group name="SPARK_CLIENTS" title="Spark Clients">
> <skippable>true</skippable>
> <service name="SPARK">
> <component>SPARK_CLIENT</component>
> </service>
> </group>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)