Driven Agent Guide: Troubleshooting the Driven Agent

version 2.2.6

1. Prerequisites: 1.1. Check your team’s demands and expectations

1.2. Check your system privileges and network access
2. Installing the Driven Agent: 2.1. Downloading the Driven Agent

2.2. Installing the Driven Agent

2.3. Confirming Installation
3. Configuring the Driven Agent: 3.1. Testing the Agent

3.2. Agent Common Options

3.3. Agent Advanced Options
4. Driven Agent for MapReduce: 4.1. Running on Hadoop or YARN

4.2. MapReduce Versions
5. Driven Agent for Hive: 5.1. Hive Version Requirements

5.2. Metadata Support

5.3. Using the Hive Agent Artifact

5.4. What Cluster Work Is Monitored
6. Driven Agent for Apache Spark: 6.1. Spark Version Requirements

6.2. Supported APIs

6.3. Spark Runtimes

6.4. Supported Runtimes
7. Using Driven Agent with Apache Oozie: 7.1. Driven Agent Configuration
8. Advanced Installation: 8.1. Scripted Installation

8.2. Amazon Elastic MapReduce
9. Troubleshooting the Driven Agent: 9.1. Applications cannot send data to the Driven Server

Troubleshooting the Driven Agent

This Troubleshooting section is a list of tips for solving common issues that users encounter while running applications using the Driven Agent.

If you still have problems after reading this page, feel free to post your queries to Driven Forums or email us at support@concurrentinc.com.

If your issue is not covered here, see the following chapter:

Note	The Driven Agent is an adapter for the Driven Plugin, many configuration options and troubleshooting issues can be resolved by changing Plugin configuration values.

This happens when your client application cannot communicate to the Driven Server.

Verify that your Driven application is up by logging in to the web browser interface and visiting the server health page.
Ensure that the Driven server host location is reachable from your Hadoop cluster.