Skip to content

Collibra API Retry

The connector retries transient Collibra API failures with exponential backoff and jitter. Network errors and HTTP 429, 502, 503, and 504 are retried. Authentication errors (401, 403) and not-found (404) are not retried, and interrupted requests are not retried.

Configuration

PolicySync Property Description Default
collibra.tag.sync.api.retry.max.attempts Maximum number of attempts per Collibra API request. 3
collibra.tag.sync.api.retry.backoff.ms Base backoff between retries, in milliseconds. The delay grows exponentially per attempt and adds random jitter to avoid synchronized retries across connector instances. 2000

These properties do not have dedicated Privacera Manager variables. Override them through the connector's custom properties file. See Configuring Custom Properties for Connectors for the full workflow.

  1. SSH to the instance where Privacera Manager is installed.

  2. Navigate to the connector instance directory and create a custom directory if it does not exist.

    If you have multiple connectors, then replace instance1 with the appropriate connector instance name.

    Bash
    1
2
    cd ~/privacera/privacera-manager/config/custom-vars/connectors/collibra/instance1
mkdir -p custom

  3. Add the following properties to connector-custom.properties (replace 0 with the connector index if different):

    Properties
    1
2
    ranger.policysync.connector.0.collibra.tag.sync.api.retry.max.attempts=3
ranger.policysync.connector.0.collibra.tag.sync.api.retry.backoff.ms=2000

  4. Once the properties are configured, run the following commands to update your Privacera Manager platform instance:

    Step 1 - Setup which generates the helm charts. This step usually takes few minutes.

    Bash
    1
2
    cd ~/privacera/privacera-manager
./privacera-manager.sh setup
    Step 2 - Apply the Privacera Manager helm charts.
    Bash
    1
2
    cd ~/privacera/privacera-manager
./pm_with_helm.sh upgrade
    Step 3 - (Optional) Post-installation step which generates Plugin tar ball, updates Route 53 DNS and so on. This step is not required if you are updating only connector properties.

    Bash
    1
2
    cd ~/privacera/privacera-manager
./privacera-manager.sh post-install