[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603285#comment-15603285 ] Hudson commented on AMBARI-17981: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5859 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5859/]) AMBARI-17981. Integrate Druid with Ambari (Nishant Bangarwa, Slim (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dcbd2c07c8fdb9db22d11ac94aea3df9bc27595c]) * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/status_params.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-broker.xml * (add) ambari-server/src/test/python/stacks/2.6/configs/default.json * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/metainfo.xml * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/overlord.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/historical.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/middlemanager.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid_node.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/router.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-coordinator.xml * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-middlemanager.xml * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-historical.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/kerberos.json * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-env.xml * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/coordinator.py * (add) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-logrotate.xml * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/service_check.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-overlord.xml * (add) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-log4j.xml * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-router.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/role_command_order.json * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/themes/theme.json * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-common.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/metainfo.xml * (add) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/broker.py > 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603178#comment-15603178
]
Swapan Shridhar commented on AMBARI-17981:
--
*Commits:*
trunk:
{code}
commit dcbd2c07c8fdb9db22d11ac94aea3df9bc27595c
Author: Swapan Shridhar
Date: Mon Oct 24 13:47:51 2016 -0700
AMBARI-17981. Integrate Druid with Ambari (Nishant Bangarwa, Slim Bouguerra
via Swapan Shridhar).
{code}
branch-2.5:
{code}
commit 11cd923735b548bf459d0f2cd96ffd7a530f56f7
Author: Swapan Shridhar
Date: Mon Oct 24 13:47:51 2016 -0700
AMBARI-17981. Integrate Druid with Ambari (Nishant Bangarwa, Slim Bouguerra
via Swapan Shridhar).
{code}
> 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602309#comment-15602309
]
Hadoop QA commented on AMBARI-17981:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834783/AMABARI-17981.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8981//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8981//console
This message is automatically generated.
> 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602104#comment-15602104 ] Nishant Bangarwa commented on AMBARI-17981: --- [~swapanshridhar] failures seem related to whitespace in config files. have updated the patch. Thanks [~bslim] for providing the fix. > 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15596055#comment-15596055
]
Swapan Shridhar commented on AMBARI-17981:
--
Trunk failure :
https://builds.apache.org/job/Ambari-trunk-Commit/5836/testReport/
branch-2.5 failure: https://builds.apache.org/job/Ambari-branch-2.5/
Revert because of test failure:
Trunk:
{code}
commit f37b518b5d29e227e56a9b2eef57673b164be22b
Author: Swapan Shridhar
Date: Fri Oct 21 12:02:38 2016 -0700
Revert "Integrate Druid with Ambari (Nishant Bangarwa, Slim Bouguerra via
Swapan Shridhar)."
This reverts commit 685e926db0d442411ab5bee50c1e189cfb0a261e.
{code}
branch-2.5:
{code}
commit 4a8544c5d54e41c20f3a2109170e84fe050e419b
Author: Swapan Shridhar
Date: Fri Oct 21 12:09:25 2016 -0700
Revert "Integrate Druid with Ambari (Nishant Bangarwa, Slim Bouguerra via
Swapan Shridhar)."
This reverts commit fca146a5d4284a8156ff3bcf468af7388a8283fe.
{code}
CC [~adoroszlai]
[~bslim] [~nishantbangarwa] Please look into the failure and fix it.
> 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15592698#comment-15592698
]
Swapan Shridhar commented on AMBARI-17981:
--
*Commits:*
*trunk:*
{code}
commit 685e926db0d442411ab5bee50c1e189cfb0a261e
Author: Swapan Shridhar
Date: Thu Oct 20 12:04:24 2016 -0700
Integrate Druid with Ambari (Nishant Bangarwa, Slim Bouguerra via Swapan
Shridhar).
{code}
*branch-2.5:*
{code}
commit fca146a5d4284a8156ff3bcf468af7388a8283fe
Author: Swapan Shridhar
Date: Thu Oct 20 12:04:24 2016 -0700
Integrate Druid with Ambari (Nishant Bangarwa, Slim Bouguerra via Swapan
Shridhar).
{code}
> 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15591966#comment-15591966
]
Hadoop QA commented on AMBARI-17981:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834347/ambari-17981.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8935//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8935//console
This message is automatically generated.
> 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
> Labels: features
> 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15591150#comment-15591150 ] Nishant Bangarwa commented on AMBARI-17981: --- removed 2.5 version, could not find 2.6 in the version list. > 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 > Labels: features > 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15590257#comment-15590257 ] slim bouguerra commented on AMBARI-17981: - this is suppose to go against ambari stack 2.6 not 2.5 thought ? > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nishant Bangarwa > Labels: features > 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575984#comment-15575984
]
Hadoop QA commented on AMBARI-17981:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833341/ambari-17981.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8877//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8877//console
This message is automatically generated.
> Integrate Druid With Ambari
> ---
>
> Key: AMBARI-17981
> URL: https://issues.apache.org/jira/browse/AMBARI-17981
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nishant Bangarwa
> Labels: features
> 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549530#comment-15549530
]
Hadoop QA commented on AMBARI-17981:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831771/ambari-17981.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8817//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8817//console
This message is automatically generated.
> Integrate Druid With Ambari
> ---
>
> Key: AMBARI-17981
> URL: https://issues.apache.org/jira/browse/AMBARI-17981
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nishant Bangarwa
> Labels: features
> 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15548519#comment-15548519
]
Hadoop QA commented on AMBARI-17981:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831724/ambari-17981.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8810//console
This message is automatically generated.
> Integrate Druid With Ambari
> ---
>
> Key: AMBARI-17981
> URL: https://issues.apache.org/jira/browse/AMBARI-17981
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nishant Bangarwa
> Labels: features
> 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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408031#comment-15408031 ] Nishant Bangarwa commented on AMBARI-17981: --- https://reviews.apache.org/r/50803/ > 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 > Labels: features > Attachments: ambari-17987.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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407988#comment-15407988
]
Hadoop QA commented on AMBARI-17981:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12822064/ambari-17987.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8289//console
This message is automatically generated.
> 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
> Labels: features
> Attachments: ambari-17987.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)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402674#comment-15402674 ] Amey commented on AMBARI-17981: --- Can't this be developed as a separate custom service? User can install as per the need? > 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 > Labels: features > > 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)
