This Quick Start guide is for readers who are new to the use of virtual machines, Apache Ambari, and/or the Apache Hadoop component stack, who would like to install and use a small local Hadoop cluster. The instructions are for a local host machine running OS X.

The following instructions cover four There are three main steps for installing Ambari and HDP using VirtualBox and Vagrant:

Install VirtualBox and Vagrant.
VirtualBox allows you to run multiple operating systems (inside multiple virtual machines) at the same time. In this Quick Start you will be using VirtualBox to run Linux on OS X.
Vagrant is a tool that makes it easier to work with virtual machines. It helps automate the work of setting up, running, and removing virtual machine environments. For our purposes, Vagrant makes it easy to install and run a preconfigured environment for running Ambari.
Start one or more VMs, each representing a node in a cluster.
Install and start one or more Linux virtual machines. Each machine represents a node in a cluster.
On one of the virtual machines, download, install, Download, install, and deploy the version of Ambari you wish to use.
From Using Ambari, deploy the version of HDP you wish to use.

When you complete the example in this Quick Start, you should have a three-node cluster of virtual machines running Ambari 2.4.1.0 and HDP 2.5.0 (unless you specify different repository versions).

Once VirtualBox and Vagrant are Once VirtualBox and Vagrant have been installed, steps 2 through 4 can be done multiple times ( to change versions, create a larger cluster, etc.).and so on. There is no need to repeat step 1 unless you want to upgrade VirtualBox and/or Vagrant later.

Note: these steps were most recently Note: these steps have been tested on MacOS 10.9.5.

Installing VirtualBox and Vagrant

...

Clone the ambari-vagrant GitHub repository into a convenient folder on your Mac. The repository contains scripts for setting up Ambari virtual machines on several Linux distributions.
From the command-line:

Code Block
git clone https://github.com/u39kun/ambari-vagrant.git

...

Edit the /etc/hosts file on your computer so that you will be able to resolve hostnames for the VMs:

Code Block
sudo -s 'cat ambari-vagrant/append-to-etc-hosts.txt >> /etc/hosts'

11.6, El Capitan.

Table of Contents

Terminology

A virtual machine, or VM, is a software program that exhibits the behavior of a separate computer and is capable of running applications and programs within its own environment.

A virtual machine is often called a guest, because it runs within another computing environment--usually known as the host. For example, if you install three Linux VMs on a Mac, the Mac is the host machine; the three Linux VMs are guests.

Multiple virtual machines can exist within a single host at one time. In the following examples, one or more virtual machines run on a host machine running OS X. OS X is the primary operating system. The virtual machines (guests) are installed under OS X. The virtual machines run Linux in separate environments on OS X. Thus, your Mac is the "host" machine, and the virtual machines that run Ambari and Hadoop are called "guest" machines.

Prerequisites

You will need the following resources for this Quick Start:

A solid internet connection, preferably with at least 5 MB available download bandwidth.
If you are installing the VMs on a Mac, at least 16 GB of memory (assuming 3 GB per VM)

Install VirtualBox and Vagrant

VirtualBox is a software virtualization package that installs on an operating system as an application. It allows you to run multiple virtual machines at the same time. In this Quick Start you will use VirtualBox to run Linux nodes within VirtualBox on OS X:

Image Added

Vagrant is a tool that makes it easier to work with virtual machines. It helps automate the work of setting up, running, and removing virtual machine environments. Using Vagrant, you can install and run a preconfigured cluster environment with Ambari and the HDP stack.

Download and install VirtualBox from https://www.virtualbox.org/wiki/Downloads. This Quick Start has been tested on version 5.1.6.
Download and install Vagrant from https://www.vagrantup.com/downloads.html .
Clone the ambari-vagrant GitHub repository into a convenient folder on your Mac. Navigate to the folder, and enter the following command from the terminal:
Code Block
git clone https://github.com/u39kun/ambari-vagrant.git
The repository contains scripts for setting up Ambari virtual machines on several Linux distributions.
Add virtual machine hostnames and addresses to the /etc/hosts file on your computer. The following command copies a set of host names and addresses from ambari-vagrant/append-to-etc-hosts.txt to the end of the /etc/hosts files:
Code Block
sudo -s 'cat ambari-vagrant/append-to-etc-hosts.txt >> /etc/hosts'

Use the vagrant command to create a private key. You will need the key for Ambari.
The vagrant command displays Vagrant command usage and common commands, and creates a private key as ~/.vagrant.d/insecure_private_key.

Code Block
vagrant

Start Linux Virtual Machines

The ambari-vagrant directory (cloned from GitHub) contains subdirectories for several Linux distributions. Each subdirectory contains a set of scripts and configuration files for running Ambari on that version of Linux.

To start one or more virtual machines:

Change your current directory to ambari-vagrant:
Code Block
cd ambari-vagrant
You will see subdirectories for different OS’s.
cd into the OS subdirectory for the OS you wish to use. CentOS 6.4 is recommended, because it is quicker to launch than other OS's.
The remainder of this Quick Start uses CentOS 6.4. To install and use another version or distribution of Linux, specify the other directory name in place of centos6.4
Code Block
cd centos6.4

Copy the private key into your OS directory:

Code Block

cp

Use the vagrant command to create a private key to use with Ambari:
Code Block
vagrant
The vagrant command displays Vagrant command information, and then it creates a private key in the file
~/.vagrant.d/insecure_private_key

.

(Optional) If you have at least 16 GM of memory on your Mac, consider increasing the amount of memory allocated to the VMs. Edit the following line in Vagrantfile, increasing 3072 to 4096 or more:
Code Block
vb.customize ["modifyvm", :id, "--memory", 3072] # RAM allocated to each VM
Start one or more VMs, using the ./up.sh command. Three seems to be a good number if you have 16GB of RAM, without taxing the system too much.
Code Block
./up.sh <# of VMs to launch>
For example, up.sh 3 starts 3 VMs.
Additional notes:
- With the default Vagrantfile (in each OS subdirectory) you can specify up to 10 VMs. (If your computer can handle it; you can even add more.)
- VMs will have fully-qualified domain names (FQDN) with the format <os-code>[01-10].ambari.apache.org, where <os-code> is c59 (CentOS 5.9), c64 (CentOS 6.4), etc. For example, c5901.ambari.apache.org, c6401.ambari.apache.org, etc.
- VMs will have IP addresses 192.168.<os-subnet>.1[01-10], where <os-subnet> is 59 for CentOS 5.9, 64 for CentOS 6.4, etc. For example, 192.168.59.101 for CentOS 5.9 node c5901, 192.168.64.101, for CentOS 6.4 node c6401, etc.
- Note that up.sh 3 is equivalent to doing something like vagrant up c640{1..3}

Testing Ambari

If it is your first time running a vagrant command, run:

Code Block
vagrant init

Log into the VM:

Code Block
vagrant ssh c6401

Note that this logs you in as user vagrant. Once you are logged in, you can run:

Code Block
sudo su -

to make yourself root. Download the repository file so that ambari-server can be installed:

Code Block

# CentOS 6 (for CentOS 7, replace centos6 with centos7 in the repo URL)
# 
#  to test public release 2.2.1
wget -O /etc/yum.repos.d/ambari.repo http://public-repo-1.hortonworks.com/ambari/centos6/2.x/updates/2.2.1.0/ambari.repo
yum install ambari-server -y
#
OR
#  to test the branch-2.2 build - updated on every commit to branch-2.2
wget -O /etc/yum.repos.d/ambari.repo http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/latest/2.2.2.0/ambaribn.repo
yum install ambari-server -y
OR
#  to test the trunk build - updated on every commit to trunk
wget -O /etc/yum.repos.d/ambari.repo http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/latest/trunk/ambaribn.repo
yum install ambari-server -y
 
# Ubuntu 12 (for Ubuntu 14, replace ubuntu12 with ubuntu14 in the repo URL)
# to test public release 2.2.1
wget -O /etc/apt/sources.list.d/ambari.list http://public-repo-1.hortonworks.com/ambari/ubuntu12/2.x/updates/2.2.1.0/ambari.list
OR
#  to test the branch-2.2 build - updated on every commit to branch-2.2
wget -O /etc/apt/sources.list.d/ambari.list http://dev.hortonworks.com.s3.amazonaws.com/ambari/ubuntu12/2.x/latest/2.2.2.0/ambaribn.list
OR 
#  to test the trunk build - updated on every commit to trunk
wget -O /etc/apt/sources.list.d/ambari.list http://s3.amazonaws.com/dev.hortonworks.com/ambari/ubuntu12/2.x/latest/trunk/ambaribn.list
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD
apt-get update
apt-get install ambari-server -y

Ambari offers many installation options (see Ambari User Guides), but to get up and running quickly with default settings, you can run the following to set up and start ambari-server.

Code Block
ambari-server setup -s ambari-server start

For frontend developers only: see Frontend Development section below for extra setup instructions.

Once Ambari Server is started, hit http://c6401.ambari.apache.org:8080 (URL depends on the OS being tested) from your browser on your local computer.
Note that Ambari Server can take some time to fully come up and ready to accept connections. Keep hitting the URL until you get the login page.

Once you are at the login page, login with the default username admin and password admin.
On the Install Options page, use the FQDNs of the VMs. For example:

Code Block
c6401.ambari.apache.org c6402.ambari.apache.org c6403.ambari.apache.org

Alternatively, you can use a range expression:

Code Block
c64[01-03].ambari.apache.org

Specify the the non-root SSH user vagrant, and upload insecure_private_key file that you copied earlier as the private key.

Follow the onscreen instructions to install your cluster.

When done testing, run vagrant destroy -f to purge the VMs.

Basic VM Operations

vagrant up <vm name>
Starts a specific VM. up.sh is a wrapper for this call.
Note: if you don’t specify the <vm name> parameter, it will try to start 10 VMs
You can run this if you want to start more VMs after you already called up.sh
For example: vagrant up c6406

vagrant destroy -f
Destroys all VMs launched from the current directory (deletes them from disk as well)
You can optionally specify a specific VM to destroy

vagrant suspend
Suspends (snapshot) all VMs launched from the current directory so that you can resume them later
You can optionally specify a specific VM to suspend

vagrant resume
Resumes all suspended VMs launched from the current directory
You can optionally specify a specific VM to resume

vagrant ssh host
Starts a SSH session to the host. For example: vagrant ssh c6401

vagrant status
Shows which VMs are running, suspended, etc.

Modifying RAM for the VMs

Each VM is allocated 2GB of RAM. These can be changed by editing Vagrantfile. To change the RAM allocation, modify the following line:

Code Block
vb.customize ["modifyvm", :id, "--memory", 2048]

Taking Snapshots

Vagrant makes it easy to take snapshots of the entire cluster.
First, install the snapshot plugin:

Code Block
vagrant plugin install vagrant-vbox-snapshot --plugin-version=0.0.2

This enables the “vagrant snapshot” command. Note that the above installs vesion 0.0.2. if you install the latest plugin version 0.0.3 does not allow taking snapshots of the whole cluster at the same time (you have to specify a VM name).
Run vagrant snapshot to see the syntax.
Note that the plugin tries to take a snapshot of all VMs configured in Vagrantfile. If you are always using 3 VMs, for example, you can comment out c64[04-10] in Vagrantfile so that the snapshot commands only operate on c64[01-03].
Note: Upon resuming a snapshot, you may find that time-sensitive services may be down (e.g, HBase RegionServer is down, etc.)

Tip: After starting the VMs but before you do anything on the VMs, run "vagrant snapshot take init". This way, you can go back to the initial state of the VMs by running "vagrant snapshot go init"; this only takes seconds (much faster than starting the VMs up from scratch by using up.sh or "vagrant up"). Another advantage of this is that you can always go back to the initial state without destroying other named snapshots that you created.

Misc

All VMs launched will have a directory called /vagrant inside the VM. This maps to the ambari-vagrant/<os> directory on your local computer. You can use this shared directory mapping to push files, etc.

If you want to test OS’s other than what’s currently in the ambari-vagrant repo, please see http://www.vagrantbox.es/ for all the readily available OS images you can test. Note that Ambari currently works on RHEL 5/6, CentOS 5/6, Oracle Linux 5/6, SUSE 11, and SLES 11. Ubuntu support is work in progress.

Pre-Configured Development Environment

Simply edit Vagrantfile to launch a VM with all the tools necessary to build Ambari from source.

Code Block
cd ambari-vagrant/centos6.4 vi Vagrantfile <- uncomment the line with "dev-bootstrap.sh" vagrant up c6401

To build from source, follow the instructions in Ambari Development.

Frontend Development

You can use this set up to develop and test out Ambari Web frontend code against a real Ambari Server on a multi-node environment.

On the host machine:

Code Block
cd ambari-vagrant/centos6.4 git clone https://git-wip-us.apache.org/repos/asf/ambari.git ambari cd ambari/ambari-web npm install brunch w

On c6401 (where Ambari Server is installed):

Code Block
cd /usr/lib/ambari-server mv web web-orig ln -s /vagrant/ambari/ambari-web/public web ambari-server restart

With this setup, whenever you change the content of ambari-web files (under ambari-vagrant/ambari/) on the host machine, brunch will pick up changes in the background and update ambari-vagrant/ambari/ambari-web/public. Because of the symbolic link, the changes are automatically picked up by Ambari Server. All you have to do is hit refresh on the browser to see the frontend code changes reflected.

Start Linux Virtual Machines

The ambari-vagrant directory (cloned from GitHub) contains several subdirectories, each for a specific Linux distribution. Each subdirectory has scripts and configuration files for running Ambari and HDP on that version of Linux.

To start one or more virtual machines:

Change your current directory to ambari-vagrant:
Code Block
cd ambari-vagrant
If you run an ls command on the ambari-vagrant directory, you will see subdirectories for several different operating systems and operating system versions.
cd into the OS subdirectory for the OS you wish to use. CentOS is recommended, because it is quicker to launch than other operating systems.

The remainder of this example uses CentOS 7.0 . (To install and use a different version or distribution of Linux, specify the other directory name in place of centos7.0.)
Code Block
cd centos7.0
Important: All VM vagrant commands operate within your current directory. Be sure to run them from the local (Mac) subdirectory associated with the VM operating system that you have chosen to use. If you attempt to run a vagrant command from another directory, it will not find the VM.

Copy the private key into the directory associated with the chosen operating system.
For this example, which uses centos7.0 , issue the following command:
Code Block
cp ~/.vagrant.d/insecure_private_key .
(Optional) If you have at least 16 GB of memory on your Mac, consider increasing the amount of memory allocated to the VMs.
Edit the following line in Vagrantfile , increasing allocated memory from 3072 to 4096 or more; for example:
Code Block
vb.customize ["modifyvm", :id, "--memory", 4096] # RAM allocated to each VM
Every virtual machine will have a directory called /vagrant inside the VM. This corresponds to the ambari-vagrant/<os> directory on your local computer, making it easy to transfer files back and forth between your host Mac and the virtual machine. If you have any files to access from within the VM, you can place them in this shared directory.
Start one or more VMs, using the ./up.sh command. Each VM will run one HDP node. Recommendation: if you have at least 16GB of RAM on your Mac and wish to run a small cluster, start with three nodes.
Code Block
./up.sh <# of VMs to launch>
For example, the following command starts 3 VMs:
./up.sh 3

On an early 2013 MacBook Pro, 2.7 GHz core i7 and 16 GB RAM, this step takes five minutes. For CentOS 7.0, the hostnames are c7001, c7002, and c7003.

Additional notes:
- If you ran the VMs before and used vagrant destroy to remove the VM's, this is the step at which you would recreate and start the VMs.
- The default Vagrantfile (in each OS subdirectory) can create up to 10 virtual machines.
- The up.sh 3 command is equivalent to vagrant up c700{1..3}.
- The fully-qualified domain name (FQDN) for each VM has the format <os-code>[01-10].ambari.apache.org, where <os-code> is c59 (CentOS 5.9), c64 (CentOS 6.4), etc. For example, c5901.ambari.apache.org will be the FQDN for node 01 running CentOS 5.9.
- The IP address for each VM has the format 192.168.<os-subnet>.1[01-10], where <os-subnet> is 64 for CentOS 6.4, 70 for CentOS 7.0, and so on. For example, 192.168.70.101 will be the IP address for CentOS 7.0 node c7001.

Check the status of your VM(s), and review any errors. The following example shows the results of ./upsh 3 for three VMs running with CentOS 7.0:

Code Block

LMBP:centos7.0 lkg$ vagrant status

Current machine states:
c7001                     running (virtualbox)
c7002                     running (virtualbox)
c7003                     running (virtualbox)
c7004                     not created (virtualbox)
c7005                     not created (virtualbox)
c7006                     not created (virtualbox)
c7007                     not created (virtualbox)
c7008                     not created (virtualbox)
c7009                     not created (virtualbox)
c7010                     not created (virtualbox)

In the preceding list, three virtual machines are installed and running.

At this point, you can snapshot the VMs to have a fresh set of running machines to reuse if desired. This is especially helpful when installing Apache Ambari and the HDP stack for the first time; it allows you to back out to fresh VMs and reinstall Ambari and HDP if you encounter errors. For more information about snapshots, see the vagrant snapshot command in "Basic Vagrant Commands," later in this Quick Start.

Access Virtual Machines

Use the following steps when you want to access a running virtual machine:

To log on to a virtual machine, use the vagrant ssh command on your host machine, and specify the hostname; for example:
Code Block
LMBP:centos7.0 lkg$ vagrant ssh c7001 Last login: Tue Jan 12 11:20:28 2016 [vagrant@c7001 ~]$
From this point onward, this terminal window is connected to the virtual machine until you exit the virtual machine. All commands go to the VM, not to your Mac.

Recommendation: Open a second terminal window for your Mac. This is useful when accessing the Ambari Web UI. To distinguish between the two, terminal windows typically list the computer name or VM hostname on each command-line prompt and at the top of the terminal window.
When you first access the VM you will be logged in as user vagrant. Switch to the root user; be sure to include the space between "su" and "-":
Code Block
[vagrant@c7001 ~]$ sudo su - Last login: Sun Sep 25 01:34:28 AEST 2016 on pts/0 root@c7001:~#

If at any time you wish to return the terminal window to your host machine:

1. Use the logout command to log out of root
2. Use the exit command to return to your host machine (Mac)

At this point, the VMs are still running in the background. You can re-issue the vagrant ssh command later, to reconnect, or you can stop the virtual machines. For more information, see the vagrant snapshot command in "Basic Vagrant Commands," later in this Quick Start.

Install Ambari on the Virtual Machines

Prerequisites: Before installing Ambari, the following software packages must be installed on your VM:

rpm
curl
wget
pdsh

On CentOS: to check if a package is installed, run yum info <package-name>. To install a package, run yum install <package-name>.

To install Ambari, you can build it yourself from source (see Ambari Development), or you can use published binaries.

As this is a Quick Start Guide to get you going quickly, ready-made publicly-available binaries are referenced. Note that these binaries were built and publicly made available via Hortonworks, a commercial vendor for Hadoop. This is for your convenience. Note that using the binaries shown here would make HDP, Hortonworks' distribution, available to be installed via Apache Ambari. The instructions here should still work (only the repo URLs need to be changed) if you have Ambari binaries from any other vendor/organization/individuals (the instructions here can be updated if anyone wanted to expand this to include such ready-made, publicly accessible binaries from any source - such contributions are welcome). This would also work if you had built the binaries yourself.

From the terminal window on the VM where you want to run the main Ambari service, download the Ambari repository. The following commands download Ambari version 2.5.1.0 and install ambari-server. To install a different version of Ambari, specify the appropriate repo URL. Choose the appropriate commands for the operating system on your VMs:

Code Block

# CentOS 6 (for CentOS 7, replace centos6 with centos7 in the repo URL)
# 
# to test public release 2.5.1
wget -O /etc/yum.repos.d/ambari.repo http://public-repo-1.hortonworks.com/ambari/centos6/2.x/updates/2.5.1.0/ambari.repo
yum install ambari-server -y
 
# Ubuntu 14 (for Ubuntu 16, replace ubuntu14 with ubuntu16 in the repo URL)
# to test public release 2.5.1
wget -O /etc/apt/sources.list.d/ambari.list http://public-repo-1.hortonworks.com/ambari/ubuntu14/2.x/updates/2.5.1.0/ambari.list
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD
apt-get update
apt-get install ambari-server -y
 
# SUSE 11 (for SUSE 12, replace suse11 with suse12 in the repo URL)
# to test public release 2.5.1
wget -O /etc/zypp/repos.d/ambari.repo http://public-repo-1.hortonworks.com/ambari/suse11/2.x/updates/2.5.1.0/ambari.repo
zypper install ambari-server -y

On an early 2013 MacBook Pro, 2.7 GHz core i7 and 16 GB RAM, this step takes seven minutes. Timing also depends on internet download speeds.

To install Ambari with default settings, set up and start ambari-server:

Code Block
ambari-server setup -s ambari-server start

To check Ambari Server status, issue the following command:
ambari-server status

After Ambari Server has started, launch a browser on your host machine (Mac). Access the Ambari Web UI at http://<hostname>.ambari.apache.org:8080. The <hostname> part of the URL specifies the VM where you installed Ambari; for example:

Code Block
http://c7001.ambari.apache.org:8080

Note: The Ambari Server can take some time to launch and be ready to accept connections. Keep trying the URL until you see the login page.

At this point, you can snapshot the VMs to have a cluster with Ambari installed, to rerun later if desired. This is especially helpful when installing Apache Ambari and the HDP stack for the first time; it allows you to back out to fresh VMs running Ambari, and reinstall a fresh HDP stack if you encounter errors. For more information about snapshots, see the vagrant snapshot command in "Basic Vagrant Commands," later in this Quick Start.

Install the HDP Stack

The following instructions describe basic steps for using Ambari to install HDP components.

On the Ambari screen, login using default username admin, password admin.
On the welcome page, choose "Launch Install Wizard."
Specify a name for your cluster, and then click Next.
On the Select Version page, choose which version of HDP to install, and then click Next.
On the Install Options page, complete the following steps:
1. List the FQDNs of the virtual machines. For example:
  Code Block
  c7001.ambari.apache.org c7002.ambari.apache.org c7003.ambari.apache.org
  Alternatively, you can use a range expression:
  Code Block
  c70[01-03].ambari.apache.org
2. Upload the insecure_private_key file that you created earlier: browse to the ambari-vagrant directory, navigate to the operating system folder for your VM's, and choose the key file.
3. Change the SSH User Account to vagrant.
4. Click "Register and Confirm."
On the Confirm Hosts page, Ambari displays installation status.
If you see a yellow banner with the following message, click on the link to review warnings:
Image Added
See the Troubleshooting section (later on this page) for more information.
When all host checks pass, close the warning window:
Image Added
Click Next to continue:
On the Choose Services page, uncheck any components that you do not expect to use. If any are required for selected components, Ambari will request to add them back in.
On the Assign Masters screen, choose hosts or simply click Next to use default values.
On the Assign Slaves and Clients screen, choose hosts or simply click Next to use default values.
On the Customize Services screen
1. Review services with warning notes, such as Hive and Ambari Metrics in the following image:
  Image Added
2. Specify missing property values (such as admin passwords) as directed by the installation wizard. When all configurations have been addressed, click Next.
On the Review screen, review the service definitions, and then click Next.
The Install, Start and Test page shows deployment status. This step takes a while; on an early 2013 MacBook Pro, 2.7 GHz core i7 and 16 GB RAM, this step takes 45 minutes.
When the cluster installs successfully, you can snapshot the VMs to have a fresh cluster with Ambari and HDP installed, to rerun later if desired. This allows you to experiment with the cluster and quickly restore back to a previous state if you wish. For more information about snapshots, see the vagrant snapshot command in "Basic Vagrant Commands," later in this Quick Start.

Troubleshooting

This subsection describes a few error conditions that might occur during Ambari installation and HDP cluster deployment:

Confirm Hosts

If you see an error similar to the following on the Confirm Hosts page of the Ambari installation wizard, click the link to see the warnings:
'Some warnings were encountered while performing checks against the 3 registered hosts above. Click here to see the warnings."

ntpd Error

On the Host Checks window, the following warning indicates that you need to start ntpd on each host:

Image Added
To start the services, for each VM navigate to a terminal window (on your Mac, vagrant ssh <VM-name>). Issue the following commands:

service ntpd start
service ntpd status

You should see messages confirming that ntpd is running. Navigate back to the Host Checks window of the Ambari installation wizard and click Rerun Checks. When all checks complete successfully, click Close to continue the installation process.

Install, Start and Test

If the Install, Start and Test step fails with the following error during DataNode deployment:

Error: Package: snappy-devel-1.0.5-1.el6.x86_64 (HDP-UTILS-1.1.0.20) Requires: snappy(x86-64) = 1.0.5-1.el6 Installed: snappy-1.1.0-3.el7.x86_64 (@anaconda/7.2)

Run the following commands under the root account on each VM:

yum remove -y snappy-1.1.0-3.el7.x86_64 yum install snappy-devel -y

Stopping and Restarting Virtual Machines

Hadoop is a complex ecosystem with a lot of status checks and cross-component messages. This can make it challenging to halt and restart several VMs and restore them later without warnings or errors.

Recommendations

If you would like to save state for a period of time and you plan to stop using your Mac during that time, if you sleep your Mac the cluster should continue from where it left off after you wake the Mac.

When stopping a set of VMs--if you don't need to save cluster state--it can be helpful to stop all services first, stop ambari-server (ambari-server stop), and then issue a Vagrant halt or suspend command.

When restarting a cluster after halting or taking a snapshot, check Ambari server status and restart it if necessary:

   ambari-server status
   ambari-server start

After logging into the Ambari Web UI, expect to see alert warnings or errors due to timeout conditions. Check the associated messages to determine whether they might affect your use of the virtual cluster. If so, it can be helpful to stop and restart one or more associated components.

Reference: Basic Vagrant Commands

The following table lists several common Vagrant commands. For more information, see Vagrant Command-Line Interface documentation.

Command	Description
Create or rebuild a VM
vagrant up <vm-name>	Create and configure guest machines. Example: `vagrant up c6406` `up.sh` is a wrapper for this call. You can use this command to start more VMs after you called `up.sh`. Note: if you do not specify the `<vm-name>` parameter, Vagrant will attempt to start ten VMs.
Tear down a VM
vagrant suspend [<vm-name>]	Save the current running state of a VM and stop the VM. A suspend effectively saves the exact point-in-time state of a machine. When you issue a `resume` command, the VM begins running immediately from that point, rather than doing a full boot. When you are ready to begin working with it again, run `vagrant up`. The machine will resume where you left off. The main benefit of `suspend` is that it is very fast; it usually takes only 5 to 10 seconds to stop and start your work. The downside is that the operation uses disk space for the VM and to store all VM state information (in RAM, when running) on disk. Optional: Specify a specific VM to suspend.
vagrant halt <vm-name>	Gracefully shut down the guest operating system and power down the VM. When you are ready to begin working with it again, use `vagrant up`. The main benefit of `halt` is that it cleanly shuts down your machine, preserves disk contents, and allows VMs to be cleanly started again. The downside is that it takes some time to restart the VM, and the guest machine still consumes disk space.
vagrant destroy -f [<vm-name>]	Remove all traces of the guest machine from your system. The `destroy` command stops the guest machine, powers it down, and removes all guest hard disks. When you are ready to begin working with it again, run `vagrant up`. The benefit of this all disk space and RAM consumed by the guest machine are reclaimed; your host machine is left clean. The downside is that the `vagrant up` operation will take extra time; rebuilding the environment takes the longest (compared with `suspend` and `halt`) because it re-imports and re-provisions the machine. Optional: Specify a specific VM to destroy.
Connect to a VM
vagrant ssh <vm-name>	Starts a SSH session to the host. Example: `vagrant ssh c6401`
Additional commands
vagrant status [<vm-name>]	Shows which VMs are running, suspended, and so on.
vagrant snapshot	A Vagrant snapshot saves the current state of a VM so that you can restart the VM from the same point at a future time. Commands include push, pop, save, restore, list, and delete. For more information, see https://www.vagrantup.com/docs/cli/snapshot.html. Note: Upon resuming a snapshot, you may find that time-sensitive services such as the (HBase RegionServer) may be down. If this happens, you will need to restart those services.
vagrant --help	List information about Vagrant commands.

Recommendation: After you start the VMs--but before you run anything on the VMs–save a snapshot. This allows you to restore the initial state of your VMs. This process is much faster than starting the VMs from scratch and then reinstalling Ambari and HDP. You can return to the initial state without destroying other named snapshots that you create later.

More information: https://www.vagrantup.com/docs/getting-started/teardown.html

If you have favorite ways of starting and stopping VMs running a Hadoop cluster, please feel free to share them in the Comments section. Thanks!

Not seeing code changes as expected? If you have run the maven command to build Ambari previously, you will see files called app.js.gz and vendor.js.gz under the public folder. You need to delete these files for the frontend code changes to be effective, as the app.js.gz and vendor.js.gz files take precedence over app.js and vendor.js, respectively.

Space shortcuts

Child pages

Versions Compared

Old Version 8

New Version Current

Key

Installing VirtualBox and Vagrant

Terminology

Prerequisites

Install VirtualBox and Vagrant

Start Linux Virtual Machines

Testing Ambari

Basic VM Operations

Modifying RAM for the VMs

Taking Snapshots

Misc

Pre-Configured Development Environment

Frontend Development

Start Linux Virtual Machines

Access Virtual Machines

Install Ambari on the Virtual Machines

Install the HDP Stack

Troubleshooting

Confirm Hosts

Install, Start and Test

Stopping and Restarting Virtual Machines

Reference: Basic Vagrant Commands

Space shortcuts

Child pages

Page History

Versions Compared

Old Version 8

New Version Current

Key

Installing VirtualBox and Vagrant

Terminology

Prerequisites

Install VirtualBox and Vagrant

Start Linux Virtual Machines

Testing Ambari

Basic VM Operations

Modifying RAM for the VMs

Taking Snapshots

Misc

Pre-Configured Development Environment

Frontend Development

Start Linux Virtual Machines

Access Virtual Machines

Install Ambari on the Virtual Machines

Install the HDP Stack

Troubleshooting

Confirm Hosts

Install, Start and Test

Stopping and Restarting Virtual Machines

Reference: Basic Vagrant Commands