You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/04/22 09:57:00 UTC
[jira] [Updated] (AMBARI-25264) Service checks mentioned in HOU
upgrade plan are run on the same node that was upgraded
[ https://issues.apache.org/jira/browse/AMBARI-25264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated AMBARI-25264:
------------------------------------
Labels: pull-request-available (was: )
> Service checks mentioned in HOU upgrade plan are run on the same node that was upgraded
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-25264
> URL: https://issues.apache.org/jira/browse/AMBARI-25264
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.2
> Reporter: Myroslav Papirkovskyi
> Assignee: Myroslav Papirkovskyi
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.6.2
>
>
> Now service checks are performed for any appropriate host during HOU. We should tune behaviour without API change to add some host selection restrictions.
> {code:java}
> [
> { "hosts": ["host1"], "service_checks": ["KAFKA", "ZOOKEEPER"] }
> ,
> { "hosts": ["host2"], "service_checks": ["ZOOKEEPER"] }
> ,
> { "hosts": ["host3", "host4"], "service_checks": ["CUSTOMSERVICE"] }
> ]
> {code}
> - Each service check will be performed for all hosts from hosts section. e.g. CUSTOMSERVICE check will be run on both host3 and host4
> - In case there is no service component on proposed host the upgrade request will be failed. This means that user should change upgrade plan and post it again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)