Resource Manager Service
The Resource Manager Service manages computing resources in the domain and dispatches jobs to achieve optimal performance and scalability. The Resource Manager Service collects information about nodes with the compute role. The service matches job requirements with resource availability to identify the best compute node to run the job.
The Resource Manager Service communicates with compute nodes in a Data Integration Service grid. Enable the Resource Manager Service when you configure a Data Integration Service grid to run jobs in separate remote processes. The Resource Manager Service does not require a license object before you enable the service.
The Resource Manager Service is highly available. High availability enables the Service Manager and the Resource Manager Service to react to network failures and failures of the Resource Manager Service. The Resource Manager Service has the restart and failover high availability feature. If a Resource Manager Service becomes unavailable, the Service Manager can restart the service on the same node or on a back-up node.
Resource Manager Service Architecture
The Resource Manager Service connects to nodes with the compute role in a Data Integration Service grid that is configured to run jobs in separate remote processes.
When the Service Manager on a node with the compute role starts, the Service Manager registers the node with the Resource Manager Service. Compute nodes use a heartbeat protocol to send periodic signals to the Resource Manager Service. The Resource Manager Service stores compute node details in memory. If the node stops sending heartbeat signals, the Resource Manager Service marks the node as unavailable and does not dispatch jobs to the node.
When you enable a Data Integration Service that runs on the grid, the Data Integration Service designates one node with the compute role as the master compute node. The Service Manager on the master compute node communicates with the Resource Manager Service to find an available worker compute node to run job requests.
Before You Enable the Resource Manager Service
Before you enable the Resource Manager Service, complete the prerequisite tasks for the service.
Before you enable the Resource Manager Service, configure a Data Integration Service grid to run jobs in separate remote processes. The designated master compute node in the grid communicates with the Resource Manager Service to find an available compute node to run jobs remotely.
Resource Manager Service Properties
To configure the Resource Manager Service properties, select the service in the Domain Navigator and click the Properties view. You can change the properties while the service is running, but you must recycle the service for the changed properties to take effect.
General Properties
In the general properties, configure the primary and back-up nodes for the Resource Manager Service.
The following table describes the general properties for the service:
Property | Description |
|---|
Name | Name of the service. You cannot change the name of the Resource Manager Service. |
Description | Description of the service. The description cannot exceed 765 characters. |
Node | Node on which the service runs. |
Backup Nodes | Nodes on which the service can run if the primary node is unavailable. |
Logging Options
The following table describes the log level property for the Resource Manager Service:
Property | Description |
|---|
Log Level | Determines the default severity level for the service logs. Choose one of the following options: - - Fatal. Writes FATAL messages to the log. FATAL messages include nonrecoverable system failures that cause the service to shut down or become unavailable.
- - Error. Writes FATAL and ERROR code messages to the log. ERROR messages include connection failures, failures to save or retrieve metadata, service errors.
- - Warning. Writes FATAL, WARNING, and ERROR messages to the log. WARNING errors include recoverable system failures or warnings.
- - Info. Writes FATAL, INFO, WARNING, and ERROR messages to the log. INFO messages include system and service change messages.
- - Trace. Write FATAL, TRACE, INFO, WARNING, and ERROR code messages to the log. TRACE messages log user request failures.
- - Debug. Write FATAL, DEBUG, TRACE, INFO, WARNING, and ERROR messages to the log. DEBUG messages are user request logs.
|
Resource Manager Service Process Properties
When the Resource Manager Service is configured to run on primary and back-up nodes, a service process is enabled on each node. Only a single process runs at any given time, and the other processes maintain standby status. You can configure the service process properties differently for each node.
To configure the Resource Manager Service process properties, select the service in the Domain Navigator and click the Processes view. You can change the properties while the service is running, but you must restart the service process for the changed properties to take effect.
Environment Variables
You can configure environment variables for the Resource Manager Service process.
The following table describes the environment variables:
Property | Description |
|---|
Environment Variable | Enter a name and a value for the environment variable. |
Advanced Options
The following table describes the advanced options:
Property | Description |
|---|
Maximum Heap Size | Amount of RAM allocated to the Java Virtual Machine (JVM) that runs the service process. Use this property to increase the performance. Append one of the following letters to the value to specify the units: - - b for bytes.
- - k for kilobytes.
- - m for megabytes.
- - g for gigabytes.
|
JVM Command Line Options | Java Virtual Machine (JVM) command line options to run Java-based programs. When you configure the JVM options, you must set the Java SDK classpath, Java SDK minimum memory, and Java SDK maximum memory properties. You must set the following JVM command line options: - - Xms. Minimum heap size. Default value is 256 m.
- - MaxPermSize. Maximum permanent generation size. Default is 128 m.
- - Dfile.encoding. File encoding. Default is UTF-8.
|
Enabling, Disabling, and Recycling the Resource Manager Service
You can enable, disable, and recycle the Resource Manager Service from the Administrator tool.
By default, the Resource Manager Service is disabled. Enable the Resource Manager Service when you configure a Data Integration Service grid to run jobs on remote nodes with the compute role. When you enable the Resource Manager Service, a service process starts on the node designated to run the service. The service is available to manage computing resources in the domain.
You might disable the Resource Manager Service if you need to perform maintenance or you need to temporarily prevent Data Integration Service jobs from remotely running on nodes with the compute role. You might recycle the Resource Manager Service if you changed a property. When you recycle the service, the Service Manager restarts the service.
When you disable a Resource Manager Service, you must choose the mode to disable it in. You can choose one of the following options:
- •Complete. Wait for all processes to complete.
- •Abort. Stop all processes immediately.
Optionally, you can choose to specify whether the action was planned or unplanned, and enter comments about the action. If you complete these options, the information appears in the Events and Command History panels in the Domain view on the Manage tab.
To enable the service, select the service in the Domain Navigator and click Enable the Service.
To disable the service, select the service in the Domain Navigator and click Disable the Service.
To recycle the service, select the service in the Domain Navigator and click Recycle the Service.
Note: If the Resource Manager Service is configured to run on primary and back-up nodes, you can enable or disable a Resource Manager Service process on the Processes view. Disabling a service process does not disable the service. Disabling a service process that is running causes the service to fail over to another node.