Configure the AEL daemon for YARN mode
An example of a fully qualified name is `websocketURL=ws://localhost:${ael.unencrypted.port}`.
</td></tr><tr><td>
**sparkHome**
</td><td>
The path to the Spark client folder on your cluster
</td></tr><tr><td>
**sparkApp**
</td><td>
The `data-integration` directory
</td></tr><tr><td>
**hadoopConfDir**
</td><td>
The directory containing the `*site.xml` files. This property value tells Spark which Hadoop/YARN cluster to use. You can download the directory containing the `*site.xml` files using the cluster management tool, or you can set the **hadoopConfDir** property to the location in the cluster.
</td></tr><tr><td>
**hadoopUser**
</td><td>
The user ID the Spark application will use. This user must have permissions to access the file in the Hadoop file system.
</td></tr><tr><td>
**hbaseConfDir**
</td><td>
The directory containing the `hbase-site.xml` file. This property value tells Spark how HBase is configured for your cluster. You can download the directory containing the `*site.xml` files using the cluster management tool, or you can set the **hadoopConfDir** property to the location in the cluster.
</td></tr><tr><td>
**sparkMaster**
</td><td>
`yarn`
</td></tr><tr><td>
**SparkDeployMode**
</td><td>
`client`**Note:** YARN-cluster deployment mode in YARN is not supported by AEL
</td></tr><tr><td>
**assemblyZip**
</td><td>
`hdfs:*$HDFS\_SPARK\_EXECUTOR\_LOCATION*`
</td></tr></tbody>
</table>3. Save and close the file.
4. Copy the `pdi-spark-executor.zip` file to your HDFS cluster, as shown in the following example:
```
$ hdfs dfs put pdi-spark-executor.zip /opt/pentaho/pdi-spark-executor.zip
```
5. Perform the following steps to start the AEL daemon.
You can start the AEL daemon by running the `daemon.sh` script. By default, this startup script is installed in the `data-integration/adaptive-execution` folder, which is referred to as the variable *PDI\_AEL\_DAEMON\_HOME*.
1. Navigate to the `data-integration/adaptive-execution` directory.
2. Run the `daemon.sh` script.
The `daemon.sh` script supports the following commands:
|Command|Action|
|-------|------|
|`daemon.sh`|Starts the daemon as a foreground process.|
|`daemon.sh start`|Starts the daemon as a background process. Logs are written to the `*PDI\_AEL\_DAEMON\_HOME*/daemon.log` file.|
|`daemon.sh stop`|Stops the daemon.|
|`daemon.sh status`|Reports the status of the daemon.|
Last updated
Was this helpful?

