Contents:
The Designer Cloud Powered by Trifacta® platform utilizes the batch job runner service to orchestrate jobs that are executed on the selected backend running environment. This service passes jobs to the backend and tracks their progress until success or failure. This service is enabled by default.
Configure Timeout
| Setting | Default Value | Description |
|---|---|---|
batchserver.spark.requestTimeoutMillis | 120000 (2 minutes) | Maximum number of milliseconds that the Batch Job Runner service should wait for a response from the Spark Job service during job execution. Default is 2 minutes. |
Configure Job Threads
As needed, you can configure the number of worker threads assigned to each process that is managed by the batch job runner. Depending of the volume and complexity of jobs that you run of each type, you may choose to modify these settings to improve performance for key job types.
Tip: These settings can be configured through the Admin Settings page in the Designer Cloud application. See Admin Settings Page.
By running environment:
| Setting | Default Value | Description |
|---|---|---|
batchserver.workers.photon.max | 2 | Number of worker threads for running Trifacta Photon jobs. This value corresponds to the maximum number of photon jobs that can be queued at the same time. For more information, see Configure Photon Running Environment. |
batchserver.workers.spark.max | 16 | Number of worker threads for running Spark jobs. For more information, see Configure Spark Running Environment. |
batchserver.workers.wrangle.max | 16 | Number of worker threads for running transformation jobs. |
By job type:
| Setting | Default Value | Description |
|---|---|---|
batchserver.workers.ingest.max | 16 | Maximum number of worker threads for running ingest jobs, which are used for loading large-scale relational data into the Transformer page. After this maximum number has been reached, subsequent requests are queued. |
batchserver.workers.profile.max | 16 | Maximum number of worker threads for running profile jobs, which provide summary and detail statistics on job results. |
batchserver.workers.publish.max | 16 | Maximum number of worker threads for running publish jobs, which deliver pre-generated job results to other datastores. |
batchserver.workers.fileconverter.max | 16 | Maximum number of worker threads for running fileconverter jobs, which are used to convert source formats into output formats. |
batchserver.workers.filewriter.max | 16 | Maximum number of worker threads for running filewriter jobs, which are used for writing file-based outputs to a specified storage location. |
Depending on your running environment, there may be additional parameters that you can configure to affect Batch Job Runner for that specific environment:
Configure BJR for EMR
Multiple BJR instances
If the Designer Cloud Powered by Trifacta platform is connected to an EMR cluster, multiple instances of the batch job runner are deployed to manage jobs across the cluster so that if one fails, YARN jobs are still tracked. No configuration is required.
YARN logs from EMR
The following properties below can be modified for batch job runner:
| Setting | Default Value | Description |
|---|---|---|
aws.emr.getLogsOnFailure | false | When set to /opt/trifacta/logs/jobs/<jobId>/container where: |
aws.emr.getLogsForAllJobs | false | When set to NOTE: This parameter is intended for debugging purposes only. |
Configure Database
The Batch Job Runner utilizes its own Jobs database. For more information, see Configure the Databases.
Logging
For more information on logging for the service, see Configure Logging for Services.
This page has no comments.