Enabling Hyperscale on a Compliance job allows it to use parallel execution across a Hyperscale cluster instead of a single Compliance Engine.
When to use this task
Use this task to enable Hyperscale processing on an existing Compliance job and configure all associated Hyperscale attributes in a single update. In the DCT UI, enabling and executing a Hyperscale job is combined into a single wizard flow.
Steps
-
Navigate to Compliance > Compliance Jobs and click the job you want to enable for Hyperscale to open its Overview page.
-
From the Actions dropdown, select Enable and Run Hyperscale Job
-
On the Configuration step:
-
Use the Select Engines dropdown to choose one or more Compliance Engines from the Hyperscale orchestrator that will participate in the job execution.
-
Configure the Source Configuration settings: Max Concurrent Source Connections, Max Records per Split, Max Split per Connection, and Max Parallel Connections per Table.
-
Configure the Target Configuration settings: Max Concurrent Target Connections and Parallelism Degree
-
Toggle options as needed: Auto Calculate Unload Split, Create All Indexes with Nologging, Disable Parallel Index Creation, and Enable All Constraints with NovalidateClick Next.
-
On the Target Configuration step, review the table list showing each table's Unload Split, Stream Size, and Column Array Rows values. Use the edit icon on individual rows to override table-level settings, or click Reset All To Default to revert all overrides. Click Next.
-
On the Summary step, review all settings.
-
Click Save and Run Hyperscale Job to enable Hyperscale on the job and immediately start execution, or click Next to save without executing.
After enabling, the job's Overview page displays Hyperscale Enabled: Yes and a new Hyperscale Job Settings tab appears alongside the existing Overview, Execution History, and Accesstabs.
What's next
Monitor the Hyperscale job execution, or if you chose to save without running, Execute the Compliance job as Hyperscale