Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Best Practices -how to stop and start Ambari services in HDP 2.3.2 in Amazon EC2

Solved Go to solution
Highlighted

Best Practices -how to stop and start Ambari services in HDP 2.3.2 in Amazon EC2

Rising Star

Hi,

I have HDP 2.3.2 cluster set up on Amazon Ec2 on RHEL 7.x .

We are stopping the Amazon cluster when not in used basically after work hours.

Can somebody share their experience, how can we start Ambari services using Amazon EC2 API or any other means.

Any other best practices which needs to be followed.

Would really appreciate your help.

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Best Practices -how to stop and start Ambari services in HDP 2.3.2 in Amazon EC2

With EC2 your challenge is the IP addresses. They will change on restart/reboot of a node, and you need to make them all static. There's no 'how to have core-site.xml update automatically', rather 'how to ensure my node doesn't move around the network on reboot'. Hope this helps.

4 REPLIES 4

Re: Best Practices -how to stop and start Ambari services in HDP 2.3.2 in Amazon EC2

@Divya Gehlot

You can use this https://gist.github.com/randerzander/5b7b0e075e59f... to stop services. You can make it part of server shutdown process.

And Cloud watch https://aws.amazon.com/about-aws/whats-new/2013/01...

Re: Best Practices -how to stop and start Ambari services in HDP 2.3.2 in Amazon EC2

Rising Star

@Neeraj Sabharwal

We are currently using Amazon EC2 API tools to start and stop the instances.and able to start the ambari server too.

But the issue now is in core-site.xml, In its still showing the old public URL for hive services.

How can we make this changes happen automatically.

Re: Best Practices -how to stop and start Ambari services in HDP 2.3.2 in Amazon EC2

Re: Best Practices -how to stop and start Ambari services in HDP 2.3.2 in Amazon EC2

With EC2 your challenge is the IP addresses. They will change on restart/reboot of a node, and you need to make them all static. There's no 'how to have core-site.xml update automatically', rather 'how to ensure my node doesn't move around the network on reboot'. Hope this helps.

Don't have an account?
Coming from Hortonworks? Activate your account here