Relationship analysis doesn't complete within the default timeout period

Shallow relationship analysis for a large set of data assets might not complete within the default timeout period.

If the number of data assets in a metadata enrichment exceeds 1,000 and you select the Set relationships enrichment option, the corresponding analysis job takes much time. It might not complete within the default timeout period of 3 days. In this case, the job run details log contains a message that is similar to the following one:

Foreign key relationship detection task (XXXX-XXXX) is in state 'Cancelled'

To allow for shallow relationship analysis of large numbers of data assets, a system administrator can increase the timeout value by setting the kill_job_after_n_hours environment variable in the wdp-profiling pod:

1. Log in to the OpenShift console by using admin credentials.
2. Go to Workloads > Deployments.
3. Search for wdp-profiling.
4. Open the deployment details by clicking the name.
5. Go to the YAML page.
6. Search for the env: section and insert the following entry replacing timeout-value as required:

   - name: kill_job_after_n_hours
     value: '<timeout-value>'
   

7. Delete the metadata-discovery pod. Wait for the pod to be back up and running.
8. Save your changes.
9. Go to Workloads > Pods.
10. Search for wdp-profiling.
11. Restart the wdp-profiling pod by deleting it.