Working with Management Packs

Management packs allow you to deploy a range of services to your Ambari-managed cluster. You can use a management pack to deploy a specific component or service.

Accessing ODP Repositories

The ODP mpacks can be accessed via the links listed below :

Installing Management Pack

In general, when working on installing management packs, perform the following steps :

  1. Download Mpack file.
  2. Install the management pack using ambari-server install-mpack --mpack=[service_mpack.gz] --verbose.
Bash
Copy
  1. Restart the Ambari Server ambari-server restart.
  2. Add service from Ambari UI.
  3. Select host(s) for respective component(s).
  4. Start all stopped or required services.

Uninstalling Management Pack

To uninstall ambari mpack, perform the following steps:

  1. Login to Ambari service UI and go to respective service section.
  2. Stop respective service and delete permanently.
  3. Uninstall the service from CLI using ambari-server uninstall-mpack --mpack-name=[service_mpack.gz].
Bash
Copy
  1. Restart the Ambari Server ambari-server restart.

Hue

Install Hue with Ambari using the following management pack created by Acceldata for ODP clusters.

Component(s)Component VersionODP Stack VersionBinary URL
Apache Ambari2.7.8.x3.2.3.1-2
Apache Hue4.10.03.2.3.1-2
  • Version Key: hue-4.10.0.3.2.2.0-2.tar.gz - Hue-4.10.0 mpack, compatible with ODP 3.2.3.1-2 release.
  • Usage Notes: Minimal installation requires Ambari, HDFS, Hive, Tez, Yarn, and Zookeeper.

Install Hue Mpack

To install Ambari Hue Mpack, perform the following:

  1. Download the branch from the code and zip with tar.gz extension.
  2. Upload the gzipped file to the ambari-server.
  3. Execute the below command for installation:
Bash
Copy
  1. Login to the Ambari UI and navigate to Add Hue service.
  2. Select the hosts for Hue Server components.
  3. Start all stopped or required services.

Hue Custom Database

To create a Hue custom database, perform the following:

  1. Get the database details.
  2. Create the Hue database and configure the Hue user along with your own password.

Example Using Hue with MySQL

  1. Create a new user in MySQL:
  • Log in to MySQL as the root user:
Bash
Copy
  • Create a new database for Hue:
SQL
Copy
  • Create a new user for Hue:
SQL
Copy
  • Grant all privileges to the new user on all databases:
SQL
Copy
  • Flush privileges to apply changes:
Bash
Copy

Note Ensure to replace $HUEUSER with the desired Hue username and $HUEPASSWORD with the desired Hue user password.

Uninstall Hue Mpack

To uninstall Ambari Hue Mpack, perform the following steps:

  1. Login to Ambari Service and Navigate to Hue Section:

    • Access the Ambari service web interface.
    • Navigate to the Hue section in the Ambari dashboard.
  2. Stop the Hue Service and Delete Permanently:

    • Locate the option to stop the Hue service in the Ambari dashboard.
    • Stop the Hue service and confirm the action.
    • Delete the Hue service permanently from the Ambari dashboard.
  3. Open a terminal or command prompt on the Ambari server.

    • Run the following command to uninstall the Hue Mpack:
Bash
Copy

Replace hue-ambari.mpack with the actual name of the Hue Mpack if it differs.

  1. Restart the Ambari Server:
    • After uninstalling the Hue Mpack, restart the Ambari server to apply the changes.
Bash
Copy

These steps will uninstall the Ambari Hue Mpack from your Ambari service.

Troubleshooting Steps for Hue Known Issues

Issue: A bug exists in User Group Management for Ambari 2.8 & ODP 3.x.

Workaround: Execute the following Python command before installing Hue:

Bash
Copy

Make sure to replace [CLUSTER_NAME] and [CLUSTER_FQDN] with the correct values for your cluster.

Impala

Install Impala with Ambari using the following management pack created by Acceldata for ODP clusters.

Component(s)Component VersionODP Stack VersionBinary URL
Apache Ambari2.7.8.x3.2.3.1-2
Apache Impala4.1.23.2.3.1-2

Install Impala Mpack

To install Impala Mpack, perform the following steps:

  1. Download the branch from the code repository and compress it into a tar.gz file.
  2. Upload the compressed file to the Ambari server.
  3. Execute the following command to install the Mpack:
Bash
Copy
  1. Restart the Ambari server:
Bash
Copy
  1. Log in to the Ambari UI and navigate to Add Impala service.
  2. Select hosts for the Catalog & Statestore components.
  3. Choose daemons from the host list and proceed with service deployment to complete the installation.
  4. Start any stopped or required services to finalize the installation.

Uninstall Impala Mpack

To uninstall Ambari Impala Mpack, perform the following:

  1. Login to Ambari Service and Navigate to Impala Section:

    • Access the Ambari service web interface.
    • Navigate to the Impala section in the Ambari dashboard.
  2. Stop the Impala Service and Delete Permanently:

    • Locate the option to stop the Impala service in the Ambari dashboard.
    • Stop the Impala service and confirm the action.
    • Delete the Impala service permanently from the Ambari dashboard.
  3. Execute Uninstallation Command:

    • Open a terminal or command prompt on the Ambari server.
    • Run the following command to uninstall the Impala Mpack:
Bash
Copy

Replace ambari-impala-mpack with the actual name of the Impala Mpack if it differs.

  1. Restart the Ambari Server:
    • After uninstalling the Impala Mpack, restart the Ambari server to apply the changes:
Bash
Copy

These steps will uninstall the Ambari Impala Mpack from your Ambari service.

Troubleshooting Steps for Impala Known Issues

  1. Issue 1: Ranger Authorization Enablement

The file ranger-hive-security.xml is missing in all daemons except on Hive servers, leading to start failures. Additionally, if audit is enabled, the file ranger-hive-audit.xml is also unavailable.

Bash
Copy

Solution

Copy the ranger-hive-security.xml and ranger-hive-audit.xml files from hive-servers to /etc/hive/conf/ as enabled with Ranger.

  1. Issue 2: Solr Audit Enablement

When Solr is enabled for Ranger audit, daemons fail to start on infra-solr-clients due to broken symlinks in the underlying impala-solr libraries.

Solution

To resolve the issue of broken symlinks for Solr in the impala-solr libraries, install ambari-infra-solr on all daemons.

  1. Issue 3: Missing Ranger Cache Policies

Missing cache policies on other launched daemons or Impala components.

Bash
Copy

Solution

Create Ranger policy cache directories under /etc/ranger/conf and copy the policy cache files from the respective policy directories.

Accessing Impala Web UI Consoles

Each of the Impala daemons (impalad, statestored, and catalogd) includes a built-in web server that displays diagnostic and status information.

Catalogd WebUI Console

The catalogd Web UI includes information about the databases, tables, and other objects managed by Impala, in addition to the resource usage and configuration settings of the catalogd. Because there is only a single instance of the catalogd within any Impala cluster, you access the Web UI only on the particular host that serves as the Impala Catalog Server.

Bash
Copy

Statesoted WebUI Console

The statestored Web UI includes information about memory usage, configuration settings, and ongoing health checks performed by statestored. Because there is only a single instance of the statestored within any Impala cluster, you can access the Web UI only on a particular host that serves as the Impala StateStore.

Bash
Copy

Impald WebUI Console

The impalad Web UI includes information about configuration settings, running and completed queries, and associated performance and resource usage for queries. In particular, the Details link for each query displays alternative views of the query including a graphical representation of the plan, and the output of the EXPLAIN, SUMMARY, and PROFILE statements from impala-shell. Each host that runs the impalad daemon has its own instance of the Web UI, with details about those queries for which that host served as the coordinator. The impalad Web UI is primarily used for diagnosing query problems that can be traced to a particular node.

Bash
Copy

For more information about accessing the Impala Web interface, see Impala Web User Interface for Debugging.

NiFi

Install NiFi with Ambari using the following management pack created by Acceldata for ODP clusters.

Component(s)Component Version
Apache Ambari2.7.8.x
Apache Nifi1.23.2
Apache Nifi-Registry1.23.2

Version Key

  • nifi-1.23.2.tar.gz - Nifi-1.23.2 mpack

Usage Notes

  • Minimal installation requires Ambari, HDFS, and Zookeeper.

Install NiFi Mpack

To install Ambari NiFi Mpack, perform the following steps:

  1. Download the branch from the code repository and compress it into a tar.gz file.
  2. Upload the compressed file to the Ambari server.
  3. Execute the following command to install the Mpack:
Bash
Copy
  1. Restart the Ambari server:
Bash
Copy
  1. Log in to the Ambari UI and navigate to Add NiFi service.
  2. Select hosts for the NiFi components.
  3. Start any stopped or required services to finalize the installation.

Uninstall NiFi Mpack

To uninstall Ambari NiFi Mpack, perform the following steps:

  1. Log in to Ambari Service and Navigate to NiFi Section:

    • Access the Ambari service web interface.
    • Navigate to the NiFi section in the Ambari dashboard.
  2. Stop the NiFi Service and Delete Permanently:

    • Locate the option to stop the NiFi service in the Ambari dashboard.
    • Stop the NiFi service and confirm the action.
    • Delete the NiFi service permanently from the Ambari dashboard.
  3. Execute Uninstallation Command:

    • Open a terminal or command prompt on the Ambari server.
    • Run the following command to uninstall the Impala Mpack:
Bash
Copy
  1. Restart the Ambari Server:
    • After uninstalling the NiFi Mpack, restart the Ambari server to apply the changes:
Bash
Copy

These steps will uninstall the Ambari NiFi Mpack from your Ambari service.

Troubleshooting Steps for NiFi Known Issues

  1. Issue 1: User Group Management for Ambari 2.8 & ODP 3.x.

Solution

Run the following Python code before installing NiFi:

Bash
Copy

Replace the CLUSTER_NAME and CLUSTER_FQDN with the correct names.

Spark 3

Install Spark 3 with Ambari using this management pack created by Acceldata for ODP clusters.

Component(s)Component VersionODP Stack VersionBinary URL
Apache Ambari2.7.8.x3.2.3.1-2
Apache Spark3.3.33.2.3.1-2

Version Key

  • spark3_mpack-3.3.3.tar.gz - Spark3.3.3 mpack, compatible with ODP 3.2.3.1-2 release.

Usage Notes

  • Minimal installation requires Ambari, HDFS, Hive, Tez, Yarn, and Zookeeper.

Install Spark 3 Mpack

To install Ambari Spark 3 Mpack, perform the following steps:

  1. Download the branch from the code repository and compress it into a tar.gz file.
  2. Upload the compressed file to the Ambari server.
  3. Execute the following command to install the Mpack:
Bash
Copy

In case you find the following errors, run the following commands as mentioned:

Bash
Copy

Incase of the above failures, run the installation command:

Bash
Copy

After running the above commands, the following message is shown:

Bash
Copy
  1. Log in to the Ambari UI and navigate to Add Spark 3 service.
  2. Select hosts for the Spark thrift and client components.
  3. Start any stopped or required services to finalize the installation.

Uninstall Spark 3 Mpack

To uninstall Ambari Spark 3 Mpack, perform the following steps:

  1. Log in to Ambari Service and Navigate to Spark 3 Section:

    • Access the Ambari service web interface.
    • Navigate to the Spark 3 section in the Ambari dashboard.
  2. Stop the Spark 3 Service and Delete Permanently:

    • Locate the option to stop the Spark 3 service in the Ambari dashboard.
    • Stop the Spark 3 service and confirm the action.
    • Delete the Spark 3 service permanently from the Ambari dashboard.
  3. Execute Uninstallation Command:

    • Open a terminal or command prompt on the Ambari server.
    • Run the following command to uninstall the Spark 3 Mpack:
Bash
Copy
  1. Restart the Ambari Server:
    • After uninstalling the Spark 3 Mpack, restart the Ambari server to apply the changes:
Bash
Copy

These steps will uninstall the Ambari Spark 3 Mpack from your Ambari service.

Troubleshooting Steps for Spark 3 Known Issues

  1. Issue 1: Issue in User Group Management for Ambari 2.8 & ODP 3.x.

Solution

Run the following Python command before installing Spark 3:

Bash
Copy

Replace the [CLUSTER_NAME] __and __[CLUSTER_FQDN] in the command above with the correct names.

HttpFS

Ambari HttpFS Service

This is a straightforward Ambari extension for the HttpFS HDFS service.

Install HttpFS Mpack

To install Ambari HttpsFS Mpack, perform the following steps:

  1. Download the branch from the code repository and compress it into a tar.gz file.
  2. Upload the compressed file to the Ambari server.
  3. Execute the following command to install the Mpack:
Bash
Copy
  1. Restart the Ambari Service:
Bash
Copy
  1. Log in to the Ambari UI and navigate to Add HttpFS service.
  2. Select hosts for the Httpfs Server components.
  3. Start any stopped or required services to finalize the installation.

Uninstall HttpFS Mpack

To uninstall Ambari HttpFS Mpack, perform the following steps:

  1. Login to Ambari Service and Navigate to HttpFS Section:

    • Access the Ambari service web interface.
    • Navigate to the HttpFS section in the Ambari dashboard.
  2. Stop the HttpFS Service and Delete Permanently:

    • Locate the option to stop the HttpFS service in the Ambari dashboard.
    • Stop the HttpFS service and confirm the action.
    • Delete the HttpFS service permanently from the Ambari dashboard.
  3. Execute Uninstallation Command:

    • Open a terminal or command prompt on the Ambari server.
    • Run the following command to uninstall the HttpFS Mpack:
Bash
Copy
  1. Restart the Ambari Server:
    • After uninstalling the HttpFS Mpack, restart the Ambari server to apply the changes:
Bash
Copy

These steps will uninstall the Ambari HttpFS Mpack from your Ambari service.

Troubleshooting Steps for HttpFS Known Issues

Issue 1 : Bug in User Group Management for Ambari 2.8 & ODP 3.x.

Solution

Run the following Python command before installing HttpFS:

Bash
Copy

Ensure the correct [CLUSTER_NAME] and [CLUSTER_FQDN] names are used.

License: Apache License version 2.0

Ozone

Install Ozone with Ambari using this management pack created by Acceldata. Note Ozone provided in this distribution supports HA only.

Version Key

  • ozone-1.4.0.tar.gz - Ozone 1.4.0 mpack, compatible from ODP v3.2.3.0-2 release onwards

Usage Notes

  • Minimal install required Ambari
  • For Authentication integration it is compatible with Kerberos
  • For Authorization integration it requires Ranger with auditing disabled due to performance issues in upstream.

Install Ozone Mpack

To install Ambari Ozone Mpack, perform the following steps:

  1. Download the branch from the code repository and compress it into a tar.gz file.
  2. Upload the compressed file to the Ambari server.
  3. Execute the following command to install the Mpack:
Bash
Copy

After running the above commands, the following message is shown:

Bash
Copy
  1. Create Service Symlink directory:
Bash
Copy
  1. Restart the Ambari service:
Bash
Copy
  1. Log in to the Ambari UI and navigate to Add Ozone service.
  2. Select atleast three hosts for the Ozone Manager, three hosts for Storage Container Manager, hosts for S3 gateway, host for Recon server, and atleast three nodes for Data node.
  3. Configure Ozone as per your use case and deploy the service.
  4. Start any stopped or required services to finalize the installation.

Uninstall Ozone Mpack

To uninstall Ambari Ozone Mpack, perform the following steps:

  1. Login to Ambari Service and Navigate to Ozone Section:

    • Access the Ambari service web interface.
    • Navigate to the Ozone section in the Ambari dashboard.
  2. Stop the Ozone Service and Delete Permanently:

    • Locate the option to stop the Ozone service in the Ambari dashboard.
    • Stop the Ozone service and confirm the action.
    • Delete the Ozone service permanently from the Ambari dashboard.
  3. Execute Uninstallation Command:

    • Open a terminal or command prompt on the Ambari server.
    • Run the following command to uninstall the Ozone Mpack:
Bash
Copy
  1. Restart the Ambari Server:
    • After uninstalling the Ozone Mpack, restart the Ambari server to apply the changes:
Bash
Copy

Registry

Install Schema Registry with Ambari using this management pack created by Acceldata for ODP Clusters.

Version Key

  • registry-1.0.0.tar.gz - Registry 1.0.0 mpack, compatible from ODP v3.2.3.1-2 release onwards.

Usage Notes

  • Minimal installation requires Ambari.
  • For authentication integration, it is compatible with Knox, OAUTH2 and Kerberos.
  • For authorization integration, it requires Ranger and for audit enablement it requires HDFS.

Install Registry Mpack

To install Ambari Registry Mpack, perform the following steps:

  1. Download the branch from the code repository and compress it into a tar.gz file.
  2. Upload the compressed file to the Ambari server.
  3. Execute the following command to install the Mpack:
Bash
Copy

After running the above commands, the following message is shown:

Bash
Copy

But it requires a few symlink changes before Ambari server restart:

Bash
Copy
  1. Log in to the Ambari UI and navigate to Add Schema Registry service.
  2. Select hosts for the Registy Server components.
  3. Start any stopped or required services to finalize the installation.

Uninstall Registry Mpack

To uninstall Ambari Schema Registry Mpack, perform the following steps:

  1. Login to Ambari Service and Navigate to Schema Registry Section:

    • Access the Ambari service web interface.
    • Navigate to the Schema Registry section in the Ambari dashboard.
  2. Stop the Registry Service and Delete Permanently:

    • Locate the option to stop the Registry service in the Ambari dashboard.
    • Stop the Registry service and confirm the action.
    • Delete the Registry service permanently from the Ambari dashboard.
  3. Execute Uninstallation Command:

    • Open a terminal or command prompt on the Ambari server.
    • Run the following command to uninstall the Registry Mpack:
Bash
Copy
  1. Restart the Ambari Server:
    • After uninstalling the Registry Mpack, restart the Ambari server to apply the changes:
Bash
Copy

These steps will uninstall the Schema Registry Mpack from your Ambari service.

Airflow

Install Apache Airflow with Ambari using this management pack created by Acceldata for ODP clusters.

Version Key

  • Apache Airflow 2.8.1 - Apache Airflow 1.0.0 mpack, compatible from ODP v3.3.0 release onwards.

Usage Notes

  • Minimal installation requires Ambari.
  • For Authentication integration it is compatible with LDAP and Kerberos

Install Apache Airflow Mpack

To install Airflow Mpack, perform the following steps:

  1. Download the branch from the code repository and compress it into a tar.gz file.
  2. Upload the compressed file to the Ambari server.
  3. Execute the following command to install the Mpack:
Bash
Copy

After running the above command, the following message is shown:

Bash
Copy

Change Simlinks before restarting the Ambari Server:

Bash
Copy
  1. Log in to the Ambari UI and navigate to Add Apache Airflow service.
  2. Select hosts for the Apache Airflow server components.
  3. Start any stopped or required services to finalize the installation.

Uninstall Ambari Airflow Mpack

To uninstall Ambari Airflow Mpack, perform the following steps:

  1. Log in to Ambari Service and Navigate to Apache Airflow Section:

    • Access the Ambari service web interface.
    • Navigate to the Apache Airflow section in the Ambari dashboard.
  2. Stop the Apache Airflow Servers and Delete Permanently:

    • Locate the option to stop the Apache Airflow service in the Ambari dashboard.
    • Stop the Airflow service and confirm the action.
    • Delete the Airflow service permanently from the Ambari dashboard.
  3. Execute Uninstallation Command:

    • Open a terminal or command prompt on the Ambari server.
    • Run the following command to uninstall the Apache Airflow Mpack:
Bash
Copy
  1. Restart the Ambari Server:
    • After uninstalling the Airflow Mpack, restart the Ambari server to apply the changes:
Bash
Copy

Isilon OneFS

README for Isilon Ambari Management Pack 1.0.3.0 for OneFS

The Isilon Ambari Management Pack for OneFS is a software component that integrates OneFS as a service into a Hadoop cluster via Ambari. This management pack allows an Ambari administrator to manage OneFS as a HDFS storage service, providing native namenode and datanode capabilities similar to traditional HDFS. The management pack is OneFS release-independent and can be updated between releases if necessary.

Prerequisites

This management pack is compatible with the following OneFS versions:

  • OneFS 8.1.2
  • OneFS 8.2.0
  • OneFS 8.2.1
  • OneFS 8.2.2
  • OneFS 9.0.0

Install OneFS Mpack

To install the Isilon management pack, perform the following steps:

  1. Run the installation command:
Bash
Copy
  1. Update the symbolic links for the OneFS service:
Bash
Copy
  1. Restart the Ambari Server:
Bash
Copy

After running the above commands, you will see the following message:

Bash
Copy

To uninstall the management pack, run the following command:

Bash
Copy

Then, remove the following directories:

Bash
Copy

Important Notes

  • A performance issue with OneFS and Ambari has been identified when Apache HBase is configured. Setting the hbase.wal.provider value to filesystem resolves this issue.
  • When installing the 1.0.3.0 Ambari Management Pack on a Hadoop cluster with a new deployment of ODP, the hbase.wal.provider value will be automatically set to filesystem.
  • If the Hadoop cluster already has Ambari and HBase configured, the hbase.wal.provider value must be manually configured in the Ambari UI. Follow these steps to configure it:
    1. Log in to the Ambari UI.
    2. Click the 'HBase' service in the left panel, then click the Configs tab, and finally click the Advanced tab.
    3. In the Custom hbase-site section, look for the hbase.wal.provider key. If it does not exist, add it by clicking Add Property.
    4. Enter the following in the Properties field: hbase.wal.provider=filesystem
    5. Click ADD and then Save to save the configuration. Restart Ambari if prompted to apply the setting.

Resolved Issues

Upgrade Isilon Mpack

Run the following commands to upgrade to Isilon Ambari Management Pack 1.0.3.0 and then to restart the Ambari server:

Bash
Copy

Kudu

Install Kudu with Ambari using this management pack created by Acceldata for ODP clusters.

Installing Kudu Mpack

To install Kudu Mpack, perform the following steps:

  1. Download the branch from the code repository and compress it into a tar.gz file.
  2. Upload the compressed file to the Ambari server.
  3. Execute the following command to install the Mpack:
Bash
Copy
  1. Log on to the Ambari UI and add the Kudu service.
  2. Select the hosts for Kudu Masters and Tablet Servers. You must select at least one of each, with a recommended maximum of up to 100 tablet servers. You must select an odd number for a minimum of 3 master servers.

Uninstall Kudu Airflow Mpack

To uninstall Ambari Kudu Mpack, perform the following steps:

  1. Log in to the Ambari UI and navigate to the Kudu section.
  2. Stop the Kudu service, then delete the service.
  3. Run the following command to remove the Kudu mpack.
Bash
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
  Last updated