The 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 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 . See Admin Settings Page.
By running environment:
|2||Number of worker threads for running Photon jobs. For more information, see Configure Photon Running Environment.|
|16||Number of worker threads for running Spark jobs. For more information, see Configure Spark Running Environment.|
Number of worker threads for running transformation jobs.
By job type:
|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.|
|16|| Maximum number of worker threads for running profile jobs, which provide summary and detail statistics on job results. |
|16|| Maximum number of worker threads for running publish jobs, which deliver pre-generated job results to other datastores. |
|16|| Maximum number of worker threads for running fileconverter jobs, which are used to convert source formats into output formats. |
|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 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:
When set to in the following location:
true, YARN logs from all nodes in the EMR cluster are collected from S3 and stored on the
where: internal identifier for the job that failed.
<jobId> is the
When set to
true, YARN logs from nodes in the EMR cluster are collected and stored in the above location for all jobs, whether they succeed or fail.
NOTE: This parameter is intended for debugging purposes only.