Table of Contents

Search

  1. Preface
  2. Introduction to Big Data Management Administration
  3. Authentication
  4. Running Mappings on a Cluster with Kerberos Authentication
  5. Authorization
  6. Cluster Configuration
  7. Cloud Provisioning Configuration
  8. Data Integration Service Processing
  9. Connections
  10. Multiple Blaze Instances on a Cluster
  11. Monitoring REST API

Big Data Management Administrator Guide

Big Data Management Administrator Guide

Manage Blaze Engines

Manage Blaze Engines

The Blaze engine remains running after a mapping run. To save resources, you can set a property to stop Blaze engine infrastructure after a specified time period.
Save resources by shutting down Blaze engine infrastructure after a specified time period.
Set the infagrid.blaze.service.idle.timeout property or the infagrid.orchestrator.svc.sunset.time property. You can use the infacmd isp createConnection command, or set the property in the Blaze Advanced properties in the Hadoop connection in the Administrator tool or the Developer tool.
Configure the following Blaze advanced properties in the Hadoop connection:
infagrid.blaze.service.idle.timeout
Optional: The number of minutes that the Blaze engine remains idle before releasing the resources that the Blaze engine uses.
The value must be an integer. Default is 60.
infagrid.orchestrator.svc.sunset.time
Optional: Maximum lifetime for an Orchestrator service, in hours.
You can disable sunset by setting the property to 0 or a negative value. If you disable sunset, the Orchestrator never shuts down during a mapping run.
The value must be an integer. Default is 24 hours.
Set the value to less than the Kerberos user ticket maximum renewal time. This Kerberos policy property is usually named like "Maximum lifetime for user ticket renewal."

0 COMMENTS

We’d like to hear from you!