Hortonworks Data Platform (HDP)

Check the installation requirements for HDP and follow the below instructions to download, install, and set up Unravel for the HDP platform.

Requirements (HDP)

To deploy Unravel, ensure that your environment meets these requirements:

Single cluster
In a single cluster deployment of Unravel, you must fulfill the following requirements for an independent host:
- Be managed by Ambari/Cloudera.
- Must have Hadoop clients pre-installed and running (YARN, HDFS etc.)
- Must have no other Hadoop service or third-party applications installed.
- Accessible to only Hadoop and Unravel Admins.
Multi-cluster
In a multi-cluster deployment of Unravel, you must fulfill the following requirements, for the host on the core node and edge node:
- Core node
  - Accessible to Unravel Admins.
  - The server should be dedicated only for Unravel. Must have no other Hadoop service or third-party applications installed.
- Edge node
  - Be managed by Ambari/Cloudera.
  - Must have Hadoop clients pre-installed.
  - Must have no other Hadoop service or third-party applications installed.
  - Accessible to only Hadoop and Unravel Admins.
  - PATH includes the path to the HDFS+Hive+YARN+Spark client/gateway, Hadoop commands, and Hive commands.
  - Clock synchronization service (such as NTP) is running and in-sync with the cluster.

Hardware requirements

Minimum requirements to install Unravel:
- Cores: 8
- RAM: 96 GB
The following table lists the minimum requirements for cores, RAM, and disks for a typical environment with default data retention and lookback settings.
Jobs per day
Cores
RAM
<Installation directory>
<Data directory>
Less than
50,000
8
96 GB
8 GB free
500 GB free
50,000 to
100,000 to
16
128 GB
8 GB free
1000 GB free
Over 100,000
Contact Unravel Support
- <Installation directory> is the storage location for Unravel binaries.
- <Data directory> is used for Elasticsearch (ES) and the bundled database. By default, the data directory is unravel/data. However, you can customize the location of this directory.
  Note
  In production environments, you can put the installation directory and data directory on separate disks. Putting data directory on a separate high spin HDD with its own SATAIII (or equivalent) bus significantly increases IO bandwidth.
Architecture: x86_64

Jobs per day	Cores	RAM	<Installation directory>	<Data directory>
Less than 50,000	8	96 GB	8 GB free	500 GB free
50,000 to 100,000 to	16	128 GB	8 GB free	1000 GB free
Over 100,000	Contact Unravel Support

Create an Installation directory and grant ownership of the directory to the user who installs Unravel. This user executes all the processes involved in Unravel installation.
If you are using Kerberos, you must create a principal and keytab for Unravel daemons to use.
Unravel must have read access to these HDFS resources:
- MapReduce logs (hdfs://user/history)
- YARN's log aggregation directory (hdfs://tmp/logs)
- Spark and Spark2 event logs (hdfs://user/spark/applicationHistory and hdfs://user/spark/spark2ApplicationHistory)
- File and partition sizes in the Hive warehouse directory (typically hdfs://apps/hive/warehouse)
Unravel needs access to the YARN Resource Manager's REST API.
Unravel needs read-only access to the database used by the Hive metastore.
If you plan to use Unravel's move or kill AutoActions, the Unravel username needs to be added to YARN's yarn.admin.acl property.
Unravel needs read-only access to the Application Timeline Server (ATS).
If you're using Impala, Unravel needs access to the Cloudera Manager API. Read-only access is sufficient.

Note

All the Unravel ports can be customized. Refer to Configuring custom ports.Configuring custom ports

On the new node, open the following ports:

Port(s)	Direction	Description
3000	Both	Traffic to and from Unravel UI
3316	Both	Database traffic
4020	Both	Unravel APIs
4021	Both	Host monitoring of JMX on `localhost`
4031	Both	Database traffic
4043	In	UDP and TCP ingest traffic from the entire cluster to Unravel Server(s)
4044-4049	In	UDP and TCP ingest spares for `unravel_lr*`
4091-4099	Both	Kafka brokers
4171-4174, 4176-4179	Both	ElasticSearch; localhost communication between Unravel daemons or Unravel Servers in a multi-host deployment
4181-4189	Both	Zookeeper daemons
4210	Both	Cluster access service
HDFS ports	Both	Traffic to/from the cluster to Unravel Server(s)
Hive metadata database port	Out	For YARN only. Traffic from Hive to Unravel Server(s) for partition reporting.
8088	Out	Traffic from Unravel Server(s) to the Resource Manager API
8188	Out	Traffic from Unravel Server(s) to the ATS server(s)
11000	Out	For Oozie only. Traffic from Unravel Server(s) to the Oozie server

For HDFS, access to the NameNode and DataNode should be provided. The default value for NameNode is 8020 , and that of DataNode is 9866 and 9867. However, these can be configured to any other ports.

Services	Default port	Direction	Description
NameNode	8020	Both	Traffic to/from the cluster to Unravel servers.
DataNode	9866,9867	Both	Traffic to/from the cluster to Unravel servers.

1. Download Unravel

Important

Before you download, Unravel for your platform, ensure to get the username and password from Unravel Support.

Download the Unravel v4.7 package (RPM or Tar) using any of the following links:

RPM
https://preview.unraveldata.com/unravel/RPM/x.x.x/unravel-x.x.x.x-onpremise.rpm
md5sum
Tar
https://preview.unraveldata.com/unravel/RPM/x.x.x/unravel-x.x.x.x-onpremise.tar.gz
md5sum

You can refer to Download section to determine any specific Unravel version that you want to download.

2. Deploy Unravel binaries

Unravel binaries are shipped as a tar file as well as an RPM package. You can deploy the Unravel binaries in any directory on the server. However, the user who installs Unravel must have write permissions to the directory where Unravel binaries are deployed.

Deploy Unravel from a tar file

To deploy Unravel binaries from a tar file, do the following:

Create an Installation directory and grant ownership of the directory to the user who installs Unravel. This user executes all the processes involved in Unravel installation.
```
mkdir /path/to/installation/directory
chown -R username:groupname /path/to/installation/directory
```
For example:
```
mkdir /opt/unravel
chown -R unravel:unravelgroup /opt/unravel
```
Extract the Unravel tar file to the installation directory, which was created as part of the prerequisite.
```
tar zxf unravel-<version>tar.gz -C /path/to/installation/directory
```
For example:
```
tar zxf unravel-<version>tar.gz -C /opt/unravel
```

Deploy Unravel from an RPM package

To install Unravel from an RPM package, do the following:

Create a directory and grant ownership of the directory to a user who will run Unravel.

mkdir /path/to/installation/directory
chown -R username:groupname /path/to/installation/directory

For example:

mkdir /opt/unravel
chown -R unravel:unravelgroup /opt/unravel

Run the following command as a root user:

rpm -i unravel-<version>.rpm --prefix /path/to/installation/directory

For example:

rpm -i unravel-<version>.rpm --prefix /opt/unravel

This deploys the binaries to the specified directory.

3. Run setup

After deploying the Unravel binaries, run the setup command from the installation directory.

<Unravel installation directory>/versions/<unravel version>/setup

For example:

/opt/unravel/versions/4.7.0.0/setup

When you run the setup command for the first time, you can pass additional parameters if you are integrating an external database or changing the default data directory:

Integrate database
If the setup command is run without additional parameters, the Unravel managed PostgreSQL database is used, which is shipped with the installer. However, if you want to use Unravel managed MySQL, MariaDB, or an external database, you can pass additional parameters with the setup command.
Example:
```
<unravel_installation_directory>/versions/<build>/setup --extra /tmp/mysql
```
```
<unravel_installation_directory>/versions/<build>/setup --extra /tmp/<MySQL-directory> --external-database TYPE HOST PORT SCHEMA USERNAME PASSWORD/
```
Note
Refer to Integrate database for all the requirements and details to integrate another database.Integrate database
Change Unravel directories
All the Unravel configurations are located in the data directory. By default, the installer maintains the data directory under <Unravel installation directory>/data. However, if you want to provide a different directory for data, you can run the setup command as follows:
```
<unravel_installation_directory>/versions/<build>/setup --data-directory /the/data/directory
```
Similarly, you can configure separate directories for all the Unravel directories such as run, tmp, services, and so on by providing a configuration file.

Precheck is automatically run when you run the setup command. The precheck output displays the issues that prevent a successful installation and also provides suggestions to resolve them. You must resolve each of the issues before proceeding. <Can add link to the list of errors/issues reference>

Note

In certain situations, you can skip the precheck using the setup --skip-precheck.

For example:

/opt/unravel/versions/<Unravel version>/setup --cluster-access=abc1011.p2g.net.eu.xyz --skip-precheck

You can also skip the checks that you know can fail. For example, if you want to skip memory and Hadoop checks, run the setup command as follows:

setup --filter-precheck ~hadoop,~mem_minimum

Run --help with the setup command and any combination of the setup command for complete usage details.

<unravel_installation_directory>/versions/<Unravel version>/setup --help
<unravel_installation_directory>/manager/manager config auto --help

4. Add configurations

Run manager config auto command to automatically pull in all the Hadoop configurations. You will be prompted to provide the location and credentials for Cloudera Manager or Ambari UI.
```
<unravel_installation_directory>/manager config auto
```

If you are using Kerberos authentication, set the principal path and keytab and then enable Kerberos authentication.

<Unravel installation directory>/manager config kerberos set --keytab /etc/security/keytabs/unravel.service.keytab --principal unravel/server@example.com

<Unravel installation directory>/manager config kerberos enable

Run the following steps from the manager tool to add certificates to the Truststore:

Autodetect file format based on the extension:

<unravel_installation_directory>/manager config tls trust add
 <certificates>

Force the uploading of certificate (pem/jks/pkcs) files:

manager config tls trust add --pem <certificates>
manager config tls trust add --jks <certificates>
manager config tls trust add --pkcs12 <certificates>

Enable the Truststore

manager config tls trust <enable|disable>

You can set additional Unravel configurations either at this point or later after you start all Unravel services.Configuring Unravel

Start all the services and check the status.

<unravel_installation_directory>/manager start watch

Enable additional instrumentation for HDP.
Optionally, you can run healthcheck to verify that all the configurations and services are running successfully.
```
<unravel_installation_directory>/manager run healthcheck
```
Healthcheck is run automatically, in the backend, in intervals. You can set your email to receive the healthcheck reports.

Enable additional instrumentation for HDP

This topic explains how to configure Unravel to retrieve additional data from Hive, Tez, Spark, and Oozie, such as Hive queries, application timelines, Spark jobs, YARN resource management data, and logs. You can do this by generating Unravel's JARs and distributing them to every node that runs queries in the cluster. Later, after the JARs are distributed to the nodes, you can integrate Hive, Tez, and Spark data with Unravel.

1. Generate and distribute Unravel's Hive Hook and Spark Sensor JARs

Create a directory, for example, /usr/local/unravel-jars, for the JARs.

mkdir /usr/local/unravel-jars
chmod 775 -R /usr/local/unravel-jars/
chown root:hadoop /usr/local/unravel-jars/

Generate the JARs and specify the directory where the Jars must be saved.
```
chmod +x <Installation directory>/install_bin/services/unravel/bin/install/cluster-setup-scripts/unravel_hdp_setup.py

cd <Installation directory>/install_bin/services/unravel/bin/install/cluster-setup-scripts/usr/local/unravel/install_bin/cluster-setup-scripts/

sudo python2 unravel_hdp_setup.py --sensor-only --unravel-server <unravel-host>:3000 --spark-version <spark-version> --hive-version <hive-version> --ambari-server <ambari-host> --btrace-dir /usr/local/unravel-jars/ --hive-hook-dir /usr/local/unravel-jars/
```
Replace the values for unravel-host, spark-version, hive-version, and ambari-host with appropriate values.
For example:
```
python2 unravel_hdp_setup.py --sensor-only --unravel-server xyz66:3000 --spark-version 2.3.0 --hive-version 1.2.1 --btrace-dir /usr/local/unravel-jars/ --hive-hook-dir /usr/local/unravel-jars/
```
Tip
For unravel-host, specify the protocol (HTTP or HTTPS) and use the fully qualified domain name (FQDN) or IP address of Unravel Server. For example, https://playground3.unraveldata.com:3000.
For spark-version, use a Spark version that is compatible with this version of Unravel. For example,
spark-2.0 for Spark 2.0.x
spark-2.1 for Spark 2.1.x
spark-2.2 for Spark 2.2.x
spark-2.3 for Spark 2.3.x
spark-2.4 for Spark 2.4.x
spark-3.0 for Spark 3.0.x
For hive-version, use a Hive version that is compatible with this version of Unravel. For example,
HDP 3.x
3.1.0 for Hive 3.1.0
HDP 2.x
1.2.0 for Hive 1.2.0 or 1.2.1
0.13.0 for Hive 0.13.0
Distribute /usr/local/unravel-jars to all worker, edge, and master nodes that run the queries.
For example,
```
scp -r /usr/local/unravel-jars root@hostname:/usr/local/
```
Make sure the node can reach port 4043 of Unravel Server.

2. Configure Ambari to work with Unravel

Hive configurations
1. Import the hive hook sensor jar into the classpath
  On the Ambari UI, click Hive > Configs > Advanced > Advanced hive-env. In the hive-env template, towards the end of line, add:
```
export AUX_CLASSPATH=${AUX_CLASSPATH}:<path to unravel hive hook sensor jar>/unravel-hive-1.2.0-hook.jar 
```
  For example:
```
export AUX_CLASSPATH=${AUX_CLASSPATH}:/usr/local/unravel-jars/unravel-hive-1.2.0-hook.jar 
```
2. Configure hive hook
  On the Ambari UI, click Hive > Configs > Advanced. In the General section, search for the following hive hooks:
  hive.exec.failure.hooks
  hive.exec.post.hooks
  hive.exec.pre.hooks
  hive.exec.run.hooks
  Copy the ,com.unraveldata.dataflow.hive.hook.UnravelHiveHook, property against each of the hooks.
  Important
  Be sure to append with no space before or after the comma, for example, property=existingValue,newValue
  For example:
```
hive.exec.failure.hooks=existing-value,com.unraveldata.dataflow.hive.hook.UnravelHiveHook
hive.exec.post.hooks=existing-value,com.unraveldata.dataflow.hive.hook.UnravelHiveHook
hive.exec.pre.hooks=existing-value,com.unraveldata.dataflow.hive.hook.UnravelHiveHook
hive.exec.run.hooks=existing-value,com.unraveldata.dataflow.hive.hook.UnravelHiveHook
```
  In case you do not find these hive hooks, go to the Custom hive-site section, click Add Property and add these as key and value per line in the Properties text box.
  For example:
```
hive.exec.pre.hooks=com.unraveldata.dataflow.hive.hook.UnravelHiveHook
```
  Similarly, ensure to set com.unraveldata.host: to unravel-gateway-internal-IP-hostname from the Custom hive-site section.
3. Optional: Hive LLAP if it is enabled
  Tip
  Edit hive-site.xml manually, not through Ambari Web UI.
  - Copy the settings in Custom hive-interactive-site and paste them into /etc/hive/conf/hive-site.xml.
  - Copy the settings in Advanced hive-interactive-env and paste them into /etc/hive/conf/hive-site.xml.
Configure HDFS
Click HDFS > Configs > Advanced > Advanced hadoop-env. In the hadoop-env template, look for export HADOOP_CLASSPATH and append Unravel's JAR path as shown.
```
export HADOOP_CLASSPATH=${HADOOP_CLASSPATH}:<Unravel sensor installation directory>/unravel-hive-1.2.0-hook.jar
```
Configure the BTrace agent for Tez
From the Ambari UI, go to Tez > config > Advanced and in the General section, append the Java options below to tez.am.launch.cmd-opts and tez.task.launch.cmd-opts:
```
-javaagent:<Unravel sensor installation directory>/jars/btrace-agent.jar=libs=mr,config=tez -Dunravel.server.hostport=<unravel-host>:4043
```
Tip
In a Kerberos environment, you need to modify tez.am.view-acls property with the "run as" user or *.

Configure the Application Timeline Server (ATS)

Note

From Unravel v4.6.1.6, this step is not mandatory.

In yarn-site.xml:

yarn.timeline-service.enabled=true
yarn.timeline-service.entity-group-fs-store.group-id-plugin-classes=org.apache.tez.dag.history.logging.ats.TimelineCachePluginImpl
yarn.timeline-service.version=1.5 or yarn.timeline-service.versions=1.5f,2.0f

If yarn.acl.enable is true, add unravel to yarn.admin.acl.
In hive-env.sh, add:
```
Use ATS Logging: true
```

In tez-site.xml, add:

tez.dag.history.logging.enabled=true
tez.am.history.logging.enabled=true
tez.history.logging.service.class=org.apache.tez.dag.history.logging.ats.ATSV15HistoryLoggingService
tez.am.view-acls=unravel-"run-as"-user or *

Note

From HDP version 3.1.0 onwards, this Tez configuration must be done manually.

Configure Spark-on-Yarn
Tip
For unravel-host, use Unravel Server's fully qualified domain name (FQDN) or IP address.
For spark-version, use a Spark version that is compatible with this version of Unravel. For example,
- spark-2.0 for Spark 2.0.x
- spark-2.1 for Spark 2.1.x
- spark-2.2 for Spark 2.2.x
- spark-2.3 for Spark 2.3.x
- spark-2.4 for Spark 2.4.x
- spark-3.0 for Spark 3.0.x
1. Add the location of the Spark JARs.
  Click Spark > Configs > Custom spark-defaults > Add Property and use Bulk property add mode, or edit spark-defaults.conf as follows:
  Tip
  If your cluster has only one Spark 1.X version, spark-defaults.conf is in /usr/hdp/current/spark-client/conf.
  If your cluster is running Spark 2.X, spark-defaults.conf is in /usr/hdp/current/spark2-client/conf.
  This example uses default locations for Spark JARs. Your environment may vary.
```
spark.unravel.server.hostport=unravel-host:4043
spark.driver.extraJavaOptions=-javaagent:/usr/local/unravel-jars/btrace-agent.jar=config=driver,libs=<spark-version>
spark.executor.extraJavaOptions=-javaagent:/usr/local/unravel-jars/btrace-agent.jar=config=executor,libs=<spark-version>
spark.eventLog.enabled=true 
```
  For example:
```
spark.unravel.server.hostport=xyznode.unraveldata.com:4043
spark.driver.extraJavaOptions=-javaagent:/usr/local/unravel-jars/btrace-agent.jar=config=driver,libs=spark-2.3
spark.executor.extraJavaOptions=-javaagent:/usr/local/unravel-jars/btrace-agent.jar=config=executor,libs=spark-2.3
spark.eventLog.enabled=true 
```
  Note
  If you have multiple Spark services in the same cluster, you must set the Spark default configuration on each of them.
2. Enable Spark streaming.
Configure Oozie
1. If you are launching Spark actions:
  Copy the JAR for the Spark version you are using, for example, spark-2.3. If you copy multiple Spark JARs, Oozie won't be to launch actions.
  Ensure that the Spark event log location is configured the same as the local Spark jobs event logs' directory. In other words, Oozie must be able to locate the event log directory to store its event history logs.
2. Make sure that oozie.libpath for the Oozie shared library in HDFS is defined.
3. Copy the Hive Hook JAR and the Btrace JAR to oozie.libpath. If you don't do this, jobs controlled by Oozie 2.3+ fail.

3. Configure the Unravel Host

Define the following properties in <Unravel installation directory>/data/conf/unravel.properties. If you do not find the properties add them.

Tez.

Property/Description	Set by user	Unit	Default
com.unraveldata.yarn.timeline-service.webapp.address The HTTP address of the Timeline service web application.	Optional	string (URL)	-
com.unraveldata.yarn.timeline-service.port Timeline service port.		number	8188

Property/Description

Set by user

Unit

Default

com.unraveldata.yarn.timeline-service.webapp.address

The HTTP address of the Timeline service web application.

Optional

string

(URL)

com.unraveldata.yarn.timeline-service.port

Timeline service port.

number

8188

Note

In a multi-cluster environment, you must add these properties to the Edge node.

Set these if the Application Timeline Server (ATS) requires authentication.

Property/Description	Set by user	Unit	Default
yarn.ats.webapp.username Username required for authentication to the Application Timeline Server (if authentication is required).	Optional	string	-
yarn.ats.webapp.password Password required for authentication to the Application Timeline Server (if authentication is required).	Optional	string	-

Property/Description

Set by user

Unit

Default

yarn.ats.webapp.username

Username required for authentication to the Application Timeline Server (if authentication is required).

Optional

string

yarn.ats.webapp.password

Password required for authentication to the Application Timeline Server (if authentication is required).

Optional

string

4. Optional: Confirm that Unravel UI shows Tez data.

Run <Unravel installation directory>/install_bin/hive_test_simple.sh on the HDP cluster or on any cloud environment where hive.execution.engine=tez.
Log into Unravel server and go to the Applications page. Check for Tez jobs.
Unravel UI may take a few seconds to load Tez data.

5. Add more configurations

Learn how to set Unravel configurations and add more configurations .

Adding a new node in an existing HDP cluster monitored by Unravel

1. Generate and distribute Unravel's Hive Hook and Spark Sensor JARs

Create a directory, for example, /usr/local/unravel-jars, for the JARs.

mkdir /usr/local/unravel-jars
chmod 775 -R /usr/local/unravel-jars/
chown root:hadoop /usr/local/unravel-jars/

Generate the JARs and specify the directory where the Jars must be saved.
```
chmod +x <Installation directory>/install_bin/services/unravel/bin/install/cluster-setup-scripts/unravel_hdp_setup.py

cd <Installation directory>/install_bin/services/unravel/bin/install/cluster-setup-scripts/usr/local/unravel/install_bin/cluster-setup-scripts/

sudo python2 unravel_hdp_setup.py --sensor-only --unravel-server <unravel-host>:3000 --spark-version <spark-version> --hive-version <hive-version> --ambari-server <ambari-host> --btrace-dir /usr/local/unravel-jars/ --hive-hook-dir /usr/local/unravel-jars/
```
Replace the values for unravel-host, spark-version, hive-version, and ambari-host with appropriate values.
For example:
```
python2 unravel_hdp_setup.py --sensor-only --unravel-server xyz66:3000 --spark-version 2.3.0 --hive-version 1.2.1 --btrace-dir /usr/local/unravel-jars/ --hive-hook-dir /usr/local/unravel-jars/
```
Tip
For unravel-host, specify the protocol (HTTP or HTTPS) and use the fully qualified domain name (FQDN) or IP address of Unravel Server. For example, https://playground3.unraveldata.com:3000.
For spark-version, use a Spark version that is compatible with this version of Unravel. For example,
spark-2.0 for Spark 2.0.x
spark-2.1 for Spark 2.1.x
spark-2.2 for Spark 2.2.x
spark-2.3 for Spark 2.3.x
spark-2.4 for Spark 2.4.x
spark-3.0 for Spark 3.0.x
For hive-version, use a Hive version that is compatible with this version of Unravel. For example,
HDP 3.x
3.1.0 for Hive 3.1.0
HDP 2.x
1.2.0 for Hive 1.2.0 or 1.2.1
0.13.0 for Hive 0.13.0
Distribute /usr/local/unravel-jars to all worker, edge, and master nodes that run the queries.
For example,
```
scp -r /usr/local/unravel-jars root@hostname:/usr/local/
```
Make sure the node can reach port 4043 of Unravel Server.

2. For Oozie, copy the Hive Hook and BTrace JARs to the HDFS shared library path

If you are launching Spark actions:
1. Copy the JAR for the Spark version you are using, for example, spark-2.3. If you copy multiple Spark JARs, Oozie won't be to launch actions.
2. Ensure that the Spark event log location is configured the same as the local Spark jobs event logs' directory. In other words, Oozie must be able to locate the event log directory to store its event history logs.
Make sure that oozie.libpath for the Oozie shared library in HDFS is defined.
Copy the Hive Hook JAR and the Btrace JAR to oozie.libpath. If you don't do this, jobs controlled by Oozie 2.3+ fail.

3. If you have changed your Kerberos tokens or principal you must perform the following steps:

Update the following properties to ensure the latest Kerberos keytab file for Unravel is available on Unravel servers.
```
com.unraveldata.kerberos.principal=new principal
com.unraveldata.kerberos.keytab.path=new path
```
Make sure the new file's ownership/permission is restored to the original setup.
Restart all services.
```
sudo /etc/init.d/unravel_all.sh start
```

In this section:

Home

Hortonworks Data Platform (HDP)

Requirements (HDP)

Note

Note

1. Download Unravel

Important

2. Deploy Unravel binaries

Deploy Unravel from a tar file

Deploy Unravel from an RPM package

3. Run setup

Note

Note

4. Add configurations

Enable additional instrumentation for HDP

1. Generate and distribute Unravel's Hive Hook and Spark Sensor JARs

Tip

2. Configure Ambari to work with Unravel

Important

Tip

Tip

Note

Note

Tip

Tip

Note

3. Configure the Unravel Host

Note

4. Optional: Confirm that Unravel UI shows Tez data.

5. Add more configurations

Adding a new node in an existing HDP cluster monitored by Unravel

1. Generate and distribute Unravel's Hive Hook and Spark Sensor JARs

Tip

2. For Oozie, copy the Hive Hook and BTrace JARs to the HDFS shared library path

3. If you have changed your Kerberos tokens or principal you must perform the following steps:

Search results