ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nishant Bangarwa (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17981) Integrate Druid With Ambari
Date Mon, 24 Oct 2016 14:13:59 GMT

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

Nishant Bangarwa updated AMBARI-17981:
--------------------------------------
    Status: Open  (was: Patch Available)

> Integrate Druid With Ambari
> ---------------------------
>
>                 Key: AMBARI-17981
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17981
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nishant Bangarwa
>            Assignee: Swapan Shridhar
>              Labels: features
>             Fix For: 2.5.0
>
>         Attachments: AMABARI-17981.patch
>
>
> This task includes adding support for druid cluster provisioning via Ambari.
> Details about Druid cluster design and different node types are present here - 
> http://druid.io/docs/latest/design/design.html
> In general, Druid can be defined as a service in HDP which has following components -

> 1) Coordinator 
> 2) Overlord 
> 3) Historical 
> 4) Broker 
> 5) Middlemanager 
>  
> Druid also has external dependencies on following 
> 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster 
> 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS.
> 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a mysql instance
provisioned by ambari itself.



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

Mime
View raw message