Installing Hortonworks Hadoop Ambari Server

Installing their manager was simple enough:

Install steps here: http://ift.tt/1Dm56HJ

You can use any VM – not just the Vagrant steps described.

1. install the Hortonworks repo:

– wget http://ift.tt/1fESf8t

– cp ambari.repo /etc/yum.repos.d

2. make sure you set up your hosts file at /etc/hosts

2. install the ambari-server

– yum install ambari-server

– ambari-server setup

– just go with defaults

3. start ambari-server

– ambari-server start

– it’ll fail if your hosts file doesn’t include the hostname of the machine you’re running it on

4. in order to add machines to a cluster you need to have the ambari agent installed on each machine

– http://ift.tt/1Dm56HL

– the Ambari wizard will do it automatically ONLY if you have ssh keys installed

– if you don’t have ssh keys installed you will have to manually install the ambari agent on each machine

– wget http://ift.tt/1fESf8t

– cp ambari.repo /etc/yum.repos.d

– yum install ambari-agent

– point the agent at the Ambari server

– nano /etc/ambari-agent/conf/ambari-agent.ini

Notes:

1. The step where you register and check the servers: http://ift.tt/1tA1cuT

– Hosts will fail if you don’t have the /etc/hosts files synced up to reflect all the hosts

2. during install, you can tail -f /var/log/yum.log to see everything Ambari is installing

3. During the “Install, Start, and Test” step, I got a failure on all 3 nodes with this message: “Puppet has been killed due to timeout”. I see yum still installing stuff on each node, so I presume it’s just a case where my internet connection was too slow and it really did timeout. I’m going to let yum continue and then simply click the “retry” button in Ambari…. yeah, after waiting clear through when it installed the mysql-connector packages, I clicked the “Retry” button in Ambari – it’s progressing now.

4. This is kinda cool – it installs mysql as the backend DB for the manager and Hive.

5. It will install Nagios server and agents – again, kinda cool

6. It seems to use Puppet for deployment

7. Note the mysql install could be more secure. Run this on the mysql host at some point: mysql_secure_installation (use all defaults except the mysql root password)

Problems I encountered:

1. Not all services started right up after the install. I had to manually start a few

2. In the initial setup wizard I changed the oozie configs to use a mysql database (the one that was configured to be used for hive). However, the oozie username does not get created and neither does the database. I had to create mysql users oozie@% and oozie@horton2 (the name of the machine oozie was running on, not it was also the same host). The oozie@% wasn’t strictly necessary, but I added it for future machines I might run oozie on.

3.