Job Agents

On start, Job Agents spawn a configurable amount of Job Containers as separate system processes. Job Agents are responsible for redirecting incoming jobs from their assigned queue to the locally spawned Job Containers via REST communication. The spawned Job Containers serve solely as executing unit for RapidMiner processes. Job Containers are kept alive as long as the Job Agent application runs and will automatically shut down when the managing Job Agent shuts down.

This page outlines how to configure a Job Agent. Please refer to the architecture page to read more about the Job Agent and Job Container structure overview.

Configuration

Agent Properties

You can alter the configuration of the Job Agent by changing {homeDir}/config/agent.properties. Each property has a comment which explains what effect the configuration has on the agent and the spawned Job Containers. Besides settings like the amount of spawned Job Containers or the maximum amount of used memory per Job Container, it is also possible to configure more complex behavior outlined in the following sub-sections.

Container ports

When Job Containers are spawned as separate system processes during the Job Agent's startup, they are bound to system ports. This is necessary because the Job Agent communicates via REST endpoint with them, e.g. to redirect jobs or to retrieve a job's latest status. The Job Agent will use successive ports beginning from the defined starting port. The last port is determined by the amount of configured Job Containers, e.g. if 1000 is defined as starting port and four Job Containers should be spawned in total, the Job Agent will bind the ports 1000, 1001, 1002 and 1003. Job Containers only listen locally and are unreachable from anywhere else than localhost/127.0.0.1.

Container restart policies

By default, Job Containers will run indefinitely and not restart after a job has been executed. With this behavior, it's possible to execute huge amounts of jobs nearly instantly. A possible downside is that jobs might have an effect on each other when run sequentially. To overcome this, it is possible to assign restart policies to Job Containers. Supported restart policies are: run indefinitely, terminate after a configurable amount of executed processes and restart on a regular basis via cron expression. When a restart is invoked, the currently active job execution will be finished before the job containers are restarted. To change this behavior, it's possible to set the jobagent.restart.timeout property. The Job Agent will then kill the Job Containers forcibly after the execution time exceeds this timeout regardless if it's still running.

Graceful Job Agent shutdown

Job Agents will by default wait for all job executions to finish before shutting down. This can however be avoided by setting the Job Agent's jobagent.shutdown.timeout.

Container Properties

The content inside {homeDir}/config/rapidminer/ is going to be copied into each job directory before container start:

  • {homeDir}/config/rapidminer/.RapidMiner: Defines the execution context. Place your own configuration files into this directory if you need it for your extensions.
  • {homeDir}/config/rapidminer/rapidminer.properties: the properties in this file are going to be set as system properties for the Job Container. The agent will also add RapidMiner Server's address properties to this file automatically before the container starts. Use this file to provide your custom properties (e.g. extension properties) for the container.

You can also use the Central resource management to synchronize the execution context from the RapidMiner Server home folder.

Resources

To enable correct execution of RapidMiner processes the Job Agent uses various external resources like JDBC drivers, RapidMiner extensions, custom Java libraries, and RapidMiner Server licenses. These resources are stored within the {homeDir}/resources/ folder of the Job Agent.

Central resource management

The Job Agent's external resources are centrally managed and automatically synchronized from the RapidMiner Server instance the Job Agent is connected to. Also the Execution context will be synchronized by default to all Job Agents.

Resource management

Centrally managed Job Agent resources are stored in the resource/ folder of the RapidMiner Server home folder. Both RapidMiner Server and all connected Job Agents use the same set of resources.

To install a new or manage an existing centrally managed resources do the following:

  1. Select the resource type you want to update (JDBC, Extensions, Custom libraries)
  2. From the table below locate the path of the resource type you want to update
  3. Update the resource type by adding or removing content from the selected folder
  4. Restart RapidMiner Server. All connected Job Agents will automatically synchronize the new resource configuration from RapidMiner Server.
Type Path
JDBC <rapidminer-server-home>/resources/jdbc/
Extensions <rapidminer-server-home>/resources/extensions/
Custom libraries <rapidminer-server-home>/resources/libs/
Licenses Licenses are automatically synced to connected Job Agents on license installation via the RapidMiner Server UI
Execution context <rapidminer-server-home>/.RapidMiner/

Automatic synchronization

By default, all resources and the execution context are automatically synchronized from the RapidMiner Server instance after the Job Agent has been started. Also, the resources are synchronized after a restart of the RapidMiner Server instance.

The Job Agent downloads the resources to the type specific resource folder and overwrites all potential existing files. These type specific resource folders are:

Type Path
JDBC <jobagent-home>/resources/jdbc/
Extensions <jobagent-home>/resources/extensions/
Custom libraries <jobagent-home>/resources/libs/
Licenses <jobagent-home>/resources/licenses/
Execution context <jobagent-home>/config/rapidminer/.RapidMiner

Individual resource management

To setup a Job Agent with an individual resources that differ from the centrally managed resource set the automatic synchronization can be disabled by setting jobagent.sync.enabled = false in the config/agent.properties file. After a restart of the Job Agent it will only use the resources that are already available in the respective resource folders.

To install a new or manage an existing local resources do the following:

  1. Shutdown the Job Agent
  2. Locate the path of the resource type you want to update
  3. Update the resource type by adding or removing content from the selected folder
  4. Restart the Job Agent

Resource types

JDBC

JDBC connections can be defined in the {homeDir}/resources/jdbc/jdbc_properties.xml file.

Extensions

Extensions are provided from {homeDir}/resources/extensions/ directory.

Custom libraries

Custom libraries are Java libraries which you can be used in a RapidMiner process, for example within the Execute Script operator. You can add these libraries to the {homeDir}/resources/libs/ folder and then they are automatically available for execution.

Don't confuse custom libraries with JDBC drivers or extensions.

Licenses

The Job Agent licenses are installed in the {homeDir}/resources/licenses/ directory.

You can define the number of spawned Job Containers (jobagent.container.count) for each Job Agent and the memory per Job Container (jobagent.container.memoryLimit) in the {homeDir}/config/agent.properties file. Keep in mind that these settings need to comply with your current server license.

Execution context

The Execution context for each job are placed in {homeDir}/config/rapidminer/.RapidMiner.