Overriding the default batch size
Unless you set the batch size in the owl-env.sh script for Standalone deployments or the Helm chart for Cloud native deployments, the batch size defaults to 5. This means that the DQ Agent applies a limit of 5 Jobs that can run concurrently. This page shows you how to override the default batch size for both Standalone and Cloud native deployments.
- Standalone
- Cloud native
- Open a terminal session.
- Open the owl-env.sh file with the following command:
- Use a base64 encoder, such as the free encoder from base64encode.org, to encode your batch ID and enter the encoded value after
DEFAULT_BATCH_ID
. - Enter the following command:
- End the terminal session.
vi /home/owldq/owl/config/owl-env.sh
export DEFAULT_BATCH_ID=<your-b64enc-batch-id>
Tip Your base64 encoded string should look similar to the following example:export DEFAULT_BATCH_ID=QUdFbVlYWnNkRDRpWVpiZXZGTnBlbVU5Tkw9PQ==
export DEFAULT_BATCH_SIZE=<your-batch-size>
Tip Enter a value in <your-batch-size>
that meets the concurrency sizing requirements of your use case.
- Open a terminal session.
- Enter the following command to pass your new default values to your agent batch ID and agent batch size:
- If your Collibra DQ app is managed by an alternative Kubernetes package manager, ensure you update the owl-agent-configmap with the following variables:
- Restart the DQ agent pod to complete the updates.
- Choose one of the following options to update your DQ agent resources:
- Update the DQ agent from the user interface
- Sign in to Collibra DQ.
- Hover your cursor over the icon and click Admin Console.
The Admin Console opens. - Click Remote Agent.
The Agent Management page opens. - Click the pencil icon.
The Edit Agent modal opens. - Update Number of Executors, Executor Memory, Number of Cores, and Driver Memory according to the concurrency sizing requirements for your use case.
- Click Save.
- Update the DQ agent from the user interface
- Update the DQ agent through Helm to set your new limits
- Open a terminal session.
- In your Helm values.yaml file, update the DQ agent's
memory
andcpu
quotas according to the concurrency sizing requirements for your use case: - Perform the Helm upgrade on the existing DQ release.
- End the terminal session.
agent:
enabled: true
replicaCount: 1
nodeSelector:
key: ""
value: ""
resources:
requests:
memory: "<your-new-memory-value>"
cpu: "<your-new-cpu-value>"
limits:
memory: "<your-new-memory-value>"
cpu: "<your-new-cpu-value>"
--set global.configMap.data.agent_batch_id="default?batchSize=<your-b64enc-batch-id>"
--set global.configMap.data.agent.data="<your-batch-size>"
Tip Enter a value in <your-batch-size>
that meets the concurrency sizing requirements for your use case.
AGENT_BATCH_ID: "your-base64-encoded-value"
AGENT_BATCH_SIZE: <your-new-batch-size>
Tip Your base64 encoded string should look similar to the following example:export DEFAULT_BATCH_ID=QUdFbVlYWnNkRDRpWVpiZXZGTnBlbVU5Tkw9PQ==
Tip Enter a value in <your-batch-size>
that meets the concurrency sizing requirements for your use case.