Ambari uses FQDN and also uses FQDN for configuration values as well. ________________________________ From: Vijaya Narayana Reddy Bhoomi Reddy <[email protected]> Sent: Friday, September 18, 2015 9:54 AM To: [email protected] Subject: Re: Component placement strategy - Ambari
Thanks Sumit, would dig into the stack advisor bit. One more rudimentary question - while setting up the cluster, should the machines be configured with static IPs (elastic IPs in cloud context) mandatorily or can the machines in the cluster have dynamic IPs as Ambari considers FQDNs and does the internal mapping between IPs and FQDN? Regards Vijay On 18 Sep 2015, at 17:41, Sumit Mohanty <[email protected]<mailto:[email protected]>> wrote: ?It is pretty much encoded in the stack advisor logic. Its not translated to a document as such. It also evolves based on feedback received. You can go through the stack advisor code to get some idea. A good way is to deploy a 3/5/7 node cluster and export the blueprint. That can pretty much be used as a template. There is an effort to integrate stack advisor with blueprint as well. ________________________________ From: Vijaya Narayana Reddy Bhoomi Reddy <[email protected]<mailto:[email protected]>> Sent: Friday, September 18, 2015 7:57 AM To: [email protected]<mailto:[email protected]> Subject: Re: Component placement strategy - Ambari Thanks Sumit. But can you please explain the strategy employed by Ambari, so that in case any tweaks are required, it would be helpful. For example, if the cluster is being setup by using Blueprints, what should be the placement guidelines to be considered? Regards Vijay On 18 Sep 2015, at 15:04, Sumit Mohanty <[email protected]<mailto:[email protected]>> wrote: ?If you are using UI to deploy the cluster it will suggest a placement and configuration which is a good default. ________________________________ From: Vijaya Narayana Reddy Bhoomi Reddy <[email protected]<mailto:[email protected]>> Sent: Friday, September 18, 2015 3:37 AM To: [email protected]<mailto:[email protected]> Subject: Component placement strategy - Ambari Hi, Is there any recommendation on the components' placement across the cluster i.e. how the various Hadoop services have to be distributed across the cluster? Especially around which services need to be placed together and which two shouldn't be placed together? For example, on the machine which acts as amber server, which other components can be installed? Is there any such guideline available at the moment? Thanks & Regards Vijay The contents of this e-mail are confidential and for the exclusive use of the intended recipient. If you receive this e-mail in error please delete it from your system immediately and notify us either by e-mail or telephone. You should not copy, forward or otherwise disclose the content of the e-mail. The views expressed in this communication may not necessarily be the view held by WHISHWORKS. The contents of this e-mail are confidential and for the exclusive use of the intended recipient. If you receive this e-mail in error please delete it from your system immediately and notify us either by e-mail or telephone. You should not copy, forward or otherwise disclose the content of the e-mail. The views expressed in this communication may not necessarily be the view held by WHISHWORKS. The contents of this e-mail are confidential and for the exclusive use of the intended recipient. If you receive this e-mail in error please delete it from your system immediately and notify us either by e-mail or telephone. You should not copy, forward or otherwise disclose the content of the e-mail. The views expressed in this communication may not necessarily be the view held by WHISHWORKS.
