[
https://issues.apache.org/jira/browse/AMBARI-21674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157486#comment-16157486
]
David Clissold commented on AMBARI-21674:
-----------------------------------------
We are very interested and motivated to see this functionality work in Ambari,
and would very much like to hear opinions and suggestions from the Ambari
community about the best approaches to this. We have a few people that are
prepared to focus on this area, but we would like to make sure we are focused
on the right areas and are on the right track.
To anyone watching this: Has there been any attempt to start on this
hybridization feature before? Anyone have any recommendations, or caveats that
we should watch for?
> Ambari to support Hybrid cluster
> ---------------------------------
>
> Key: AMBARI-21674
> URL: https://issues.apache.org/jira/browse/AMBARI-21674
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-agent, ambari-server
> Reporter: Ayappan
>
> We have been exploring Hybrid hadoop cluster recently. By hybrid, i mean the
> nodes in the cluster have different platform architectures. Some nodes are
> intel x86_64 , some are IBM Power ppc64le., and so on. Right now Ambari
> doesn't have this hybrid support. It selects the repo based on the machine
> where it is installed and then ask the users to add the nodes. I think this
> order has to be changed as the first step to provide hybrid support in Ambari.
> We were actually able to bring up a hybrid cluster using some hacks (not so
> good) like manually configuring the yum repos according to the arch,
> installing the rpms before ambari does and also manipulating the JAVA_HOME
> variable. We also ran some examples like terasort without any issues.
> So the thing here is we kind of starting to work on making Ambari provide a
> smooth hybrid support which requires some design changes. We very much
> welcome Ambari community to provide some ideas, patch contributions, or
> whatever way you can help us on.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)