You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2015/06/24 18:29:04 UTC

[jira] [Created] (AMBARI-12126) Ability to schedule tasks AFTER all services installed and started

Alejandro Fernandez created AMBARI-12126:
--------------------------------------------

             Summary: Ability to schedule tasks AFTER all services installed and started
                 Key: AMBARI-12126
                 URL: https://issues.apache.org/jira/browse/AMBARI-12126
             Project: Ambari
          Issue Type: Story
          Components: ambari-server
    Affects Versions: ambari-2.1.0
            Reporter: Alejandro Fernandez
            Assignee: Alejandro Fernandez


Ambari needs to have another level where tasks can get ordered during the cluster deployment.
Today, we do,
* Install all services
* Start services according to role_command_order

However, there is one more category needed: after all services have started.

For example,
Tez tarball needs to be copied to HDFS. Right now, this is shoehorned into HiveServer2 Start and HistoryServer Start because there is no better way to do it. And for this reason, those hosts also need to contain Tez client. The only true requirement is that the Tez Client host also have HDFS Client, Yarn Client, MR Client, and for NameNode and RM to be up.




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