You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2018/01/26 15:09:00 UTC

[jira] [Updated] (AMBARI-22854) Fix running service checks with new mpack definitions

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

Dmytro Sen updated AMBARI-22854:
--------------------------------
    Status: Patch Available  (was: In Progress)

> Fix running service checks with new mpack definitions
> -----------------------------------------------------
>
>                 Key: AMBARI-22854
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22854
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> *Background*
> # New mpack composition forces us to break down our service definitions into client and server modules. This is because EDW mpack needs to be composed of HIVE, HIVE-CLIENT, ZOOKEEPER-CLIENT. EDW mpack doesnt really contain ZOOKEEPER service just ZOOKEEPER-CLIENT. Hence the new mpack structure we will have to break the ZOOKEEPER service definition into "zookeeper" server module and "zookeeper-client" client module definitions. 
> However, breaking the service definition into client and server modules would require the logic for calling service check to be updated because now to run service check for zookeeper, we will need to call ZOOKEEPER-CLIENT/ZOOKEEPER-CLIENT to run the service check. 
> cc: [~mradhakrishnan] who has more context on this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)