Why UD push job always fails with error "Push Failure Count reached threshold: " ?

Document ID:KM02951658
Creation Date:15-Sep-2017
Modified Date:18-Sep-2017
- Micro Focus Products:
  universal cmdb

Summary

Push job by itself fails if the numebr of CIs which are failed to push to the remote destination reached some specific threas hold value. This is kind of notification to user to check the result and do the corrective action as necessary.

Question

Push jobs in UD pushes the CIs into remote repositry. Usually push job continue to run even if few of the CIs failed to get pushed into the remote destination , it will skip the failed CIs and continue with the remaining CIs. If number of failed CIs reached critical threashould it fails with below error, along with the failed count. In below error message failed CI's count is 27431

Caused by: com.hp.ucmdb.synchronizer.SynchronizerException: [ErrorCode [860] Error occurred while running synchronization. See statistics for more information]
Push Failure Count reached threshold: 27431
at com.hp.ucmdb.synchronizer.operations.Abstrac

Answer

The number of failed CIs reached critical threashould it stops the push job along with below exception., along with the failed count.

Caused by: com.hp.ucmdb.synchronizer.SynchronizerException: [ErrorCode [860] Error occurred while running synchronization. See statistics for more information]
Push Failure Count reached threshold: <FAILED COUNT>
at com.hp.ucmdb.synchronizer.operations.Abstrac

This condition check is done so that, user notified about the status of the CI push job so that, corrective actoin can be taken and then rerun the job.

This behavior can be controlled by setting one of the parameter from jmx-console of UD.

The parameter which controls this behavior is replication.failures.threshold

The default value of this setting is 20000

In a push job where number of CIs being pushed in in higher value, we can increase this value if necessary from the settingServices mbean of the jmx-console