ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doroszlai, Attila (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
Date Fri, 21 Oct 2016 17:33:58 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595787#comment-15595787
] 

Doroszlai, Attila commented on AMBARI-17981:
--------------------------------------------

Hi [~swapanshridhar], could you please check the unit test that started giving error with
this commit?

https://builds.apache.org/job/Ambari-trunk-Commit/5836/testReport/

> 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: ambari-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