Configuring the Task Executor Container
The Task Executor Container is used for executing various tasks, such as building deliverables and validating the publications. You can configure the container by setting some properties:
- executor.service.ope.max.memory
- Specifies the maximum memory allocated for a single publishing build. Default value is 1024 MB.
- executor.service.validation.max.memory
- Specifies the maximum memory allocated for a single validation build. Default value is 200 MB.
- executor.service.parallel.publishing.builds
- Defines the maximum number of publishing builds that the application can execute simultaneously. This limits how many publishing processes can be handled at once, helping to manage server load and optimize resource usage. Default value is 2.
- executor.service.parallel.validation.builds
- Defines the maximum number of validation builds that the application can execute simultaneously. Controls how many validation processes can occur at the same time, ensuring efficient validation processing while balancing server performance. Default value is 5.
- executor.service.metrics.disk.store.period
- Determines how long (in days) the server should retain publishing build metrics on disk. This ensures that metrics for builds are stored for a limited time, preventing disk space overuse by automatically purging old data after the specified retention period. Default value is 30.
Example:
Sample configuration (to be added under the environment section of the
task-executor container in the
docker-compose.override.yml):
- JAVA_OPTS=-Dexecutor.service.validation.max.memory=500 -Dexecutor.service.ope.max.memory=800 -Dexecutor.service.parallel.builds.number=3 -Xmx512M