HELIX_PARTICIPANT_MAX_CONCURRENT_TASKS

Description: The property defines the maximum number of tasks that can be executed concurrently on Helix participant.

Values and behavior:

Case 1 - If the memory of the Analytical Store is manually set, the value of this property must be set to one-third of the total processing memory of the Analytical Store defined in GB.

Case 2 - If Analytical Store memory is set to the Auto mode, you must change the value of the Analytical Store. While changing the value, refer to the table mentioned below.

	HELIX_PARTICIPANT_MAX_CONCURRENT_TASKS

	HELIX_PARTICIPANT_MAX_CONCURRENT_TASKS
Worker Memory (in GB)	For Shared Query Engine	For Kubernetes Cluster
16GB	1	3
32GB	2	6
64GB	4	11
128GB	9	24

Note

For AWS, m5.4xlarge is the default instance type for the worker nodes.
For Azure, Standard_D16s_v4 is the default Worker Instance Type.
For GCP, n2-standard-16 is the minimum configuration.

Default value:
10

Scope:

Application

Comes into effect:

Requires BI Server restart to come into effect.

Environment:

Applicable in Kubernetes-based environments.