Improving reconciliation job performance
As a configuration manager, it is important to make sure that the resources powering the reconciliation process remain efficient, accurate, and fast, especially when reconciling a large number of configuration items (CIs).
For an efficient, accurate, and fast reconciliation process, the RE ID Service and the RE Merge service run the identification and merge activities in a reconciliation job on a separate Kubernetes Pod by default. This frees up the reconciliation pod for other related activities.
The RE ID Service also filters out duplicate CIs from the source dataset and excludes them from the identification activity. This exclusion makes the overall reconciliation process faster and more efficient by optimizing the resources needed to process a large number of CIs.
The RE Merge service is applicable only if the Merge Order is set to By Class in Separate Transactions in a Merge activity.
The RE ID Service and the RE Merge service is enabled by default. If you disable the RE ID Service, the identification activity runs on the same pod as the reconciliation job.
The log location depends on activities executed as part of the reconciliation job.
For example, if a reconciliation job contains Identity, Merge, and Purge activities, the identity activity logs are created in the ID service pod, the Merge activity logs in the Merge service pod, and the Purge activity logs in the recon-engine pod.
If the reconciliation job name does not contain spaces, the logs are displayed in the Mid-Tier in the AR System Management Console > AR System Server Group Console > Logs > View Logs.
If the job name contains spaces, the logs are generated in the /opt/bmc/ARSystem/db folder.
The log files have a .log extension.
To enable or disable the RE ID service
- Log in to Mid Tier.
- Select Applications > AR System Administration > AR System Administration Console > System > General > Centralized Configuration.
- From the Component Type list, select com.bmc.arsys.other > reconciliation pod name .
- In the Setting Name column, if the RE-Enable-IDService parameter is not present, click Add to add the setting.
This parameter is enabled by default and is not displayed in the Setting Name list. - In the corresponding Setting Value, enter either of the following value:
- F (False) to disable the RE ID Service feature.
- (Default) T (True) to enable the RE ID Service feature.
For information about modifying the default configurations for the RE ID Service, see Reconciliation-Engine-configuration-settings.
To enable or disable the RE Merge service
- Log in to Mid Tier.
- Select Applications > AR System Administration > AR System Administration Console > System > General > Centralized Configuration.
- From the Component Type list, select com.bmc.arsys.other > reconciliation pod name .
- In the Setting Name column, if the RE-Enable-MergeService parameter is not present, click Add to add the setting.
This parameter is enabled by default and is not displayed in the Setting Name list. - In the corresponding Setting Value, enter either of the following value:
- F (False) to disable the RE Merge Service feature.
- (Default) T (True) to enable the RE Merge Service feature.
For information about modifying the default configurations for the RE Merge Service, see Reconciliation-Engine-configuration-settings.
Settings in a reconciliation job
For a better job performance use the following settings:
| Setting | Description |
|---|---|
| Disable Progress Bar on UI During Job Execution | Select this option to run the reconciliation job without displaying the progress bar on the UI. |
| Ignore Failed CIs | Select this option to exclude the CIs that failed to reconcile in the previous run of a reconciliation job. Important: |