Documents
  • Invariant Documents
  • Platform
    • Data Platform
      • Install Overview
      • System Requirement
      • Software Requirement
      • Prepare the Environment
      • Installing Ambari Server
      • Setup Ambari Server
      • Start Ambari Server
      • Single Node Install
      • Multi-Node Cluster Install
      • Cluster Install from Ambari
      • Run and monitor HDFS
    • Apache Hadoop
      • Compatible Hadoop Versions
      • HDFS
        • HDFS Architecture
        • Name Node
        • Data Node
        • File Organization
        • Storage Format
          • ORC
          • Parquet
        • Schema Design
      • Hive
        • Data Organization
        • Data Types
        • Data Definition
        • Data Manipulation
          • CRUD Statement
            • Views, Indexes, Temporary Tables
        • Cost-based SQL Optimization
        • Subqueries
        • Common Table Expression
        • Transactions
        • SerDe
          • XML
          • JSON
        • UDF
      • Oozie
      • Sqoop
        • Commands
        • Import
      • YARN
        • Overview
        • Accessing YARN Logs
    • Apache Kafka
      • Compatible Kafka Versions
      • Installation
    • Elasticsearch
      • Compatible Elasticsearch Versions
      • Installation
  • Discovery
    • Introduction
      • Release Notes
    • Methodology
    • Discovery Pipeline
      • Installation
      • DB Event Listener
      • Pipeline Configuration
      • Error Handling
      • Security
    • Inventory Manager
      • Installation
      • Metadata Management
      • Column Mapping
      • Service Configuration
      • Metadata Configuration
      • Metadata Changes and Versioning
        • Generating Artifacts
      • Reconciliation, Merging Current View
        • Running daily reconciliation and merge
      • Data Inventory Reports
    • Schema Registry
  • Process Insight
    • Process Insight
      • Overview
    • Process Pipeline
      • Data Ingestion
      • Data Storage
    • Process Dashboards
      • Panels
      • Templating
      • Alerts
        • Rules
        • Notifications
  • Content Insight
    • Content Insight
      • Release Notes
      • Configuration
      • Content Indexing Pipeline
    • Management API
    • Query DSL
    • Configuration
  • Document Flow
    • Overview
  • Polyglot Data Manager
    • Polyglot Data Manager
      • Release Notes
    • Data Store
      • Concepts
      • Sharding
    • Shippers
      • Filerelay Container
    • Processors
    • Search
    • User Interface
  • Operational Insight
    • Operational Insight
      • Release Notes
    • Data Store
      • Concepts
      • Sharding
    • Shippers
      • Filerelay Container
    • Processors
    • Search
    • User Interface
  • Data Science
    • Data Science Notebook
      • Setup JupyterLab
      • Configuration
        • Configuration Settings
        • Libraries
    • Spark DataHub
      • Concepts
      • Cluster Setup
      • Spark with YARN
      • PySpark Setup
        • DataFrame API
      • Reference
  • Product Roadmap
    • Roadmap
  • TIPS
    • Service Troubleshooting
    • Service Startup Errors
    • Debugging YARN Applications
      • YARN CLI
    • Hadoop Credentials
    • Sqoop Troubleshooting
    • Log4j Vulnerability Fix
Powered by GitBook
On this page
  • Setup YUM repository server
  • Create Staging Directory
  • Download and Extract Ambari Tarball
  • Setup local YUM repository
  • Install Ambari Server
  1. Platform
  2. Data Platform

Installing Ambari Server

Setup YUM repository server

A YUM repository server setup is required in order to install Ambari. The repository must reside on a host which is accessible from all the cluster hosts. Use a dedicated host for this purpose or setup the YUM repository server on the admin host where the Ambari Server will be installed. To setup a new YUM repository server, a web server is needed. Make sure the web server is running on the host that will serve as a YUM repo.

Create Staging Directory

Use a staging directory where you will extract the tarballs for Ambari and Hadoop stacks. Each tarball is an archived yum repository and has setup_repo.sh script that creates a symlink from the document root of web server /var/www/html to the directory where the tarball is extracted.

The staging directory (and all the directories above it) must be readable and executable by the system user running the web process (typically apache). It is recommended to make the directory readable and executable by everyone. Please do not use /tmp directory as staging.

Download and Extract Ambari Tarball

Ambari RPMs are shipped as an archived YUM repository that should be extracted to the YUM repo server.

On the host used as a YUM repo, download the tarball into a staging directory that has been setup previously. Ensure that all the parent directories up to the staging directory have read and execute access for all users as we will be using this directory to stage the local yum repository.

Setup local YUM repository

On the host used as a YUM repo, execute a helper script setup_repo.sh shipped as a part of the ambari tarball:

/staging/AMBARI-2.1.2.2/setup_repo.sh

This script assumes that the document root of YUM repo web server is set to /var/www/html and will create a symlink like ambari-<version> there that points to the extracted ambari tarball. Verify that the ambari YUM repo is now available from the YUM web server:

curl http://localhost/AMBARI-2.1.2.2/repodata/repomd.xml 

The script also creates Ambari repo definition and places it in /etc/yum.repos.d/ambari.repo file. This file should be available on the admin host where the Ambari Server will be installed.

At this point the Invariant Ambari YUM repository should be available for the cluster hosts. Test that you can access the following URL from the admin and cluster

hosts: http://<yum.repo.fqdn>/AMBARI-2.1.2.2

Install Ambari Server

The Ambari Server is installed from RPMs by yum command:

yum install ambari-server

This command installs the Ambari Server which is a web application server listening on port 8080. It also installs a PostgreSQL server instance, that listens on port 5432.

PreviousPrepare the EnvironmentNextSetup Ambari Server

Last updated 4 years ago