How to Enable the Load Control Feature

The Load Control feature controls the load of Data Flow Probes by limiting maximum job threads for the following scenarios:

• UCMDB server is processing discovered results in an extremely slow fashion although still reachable.
• There is a large amount of unsent CIs in Data Flow Probes.

By default, this feature is disabled.

Enable the Load Control Feature

To enable the Load Control feature, do the following:

1. Open DataFlowProbe.properties.

2. Add the following lines:

   # Slow down in probe (Manager) side when the UCMDB Server is slow to response
   appilog.agent.local.services.loadcontrol.enable = true
   appilog.agent.local.services.loadcontrol.checkIntervalMsec = 300000
   # Note: below 2 parameters are optional, if they are undefined, then the behavior would be no change.
   appilog.agent.local.services.loadcontrol.maxJobThreads = 3
   appilog.agent.local.services.loadcontrol.retrievetaskResultsFromDB.minObjects=2000
   # Thresholds to trigger the load control feature
   appilog.agent.local.services.loadcontrol.thresh.resultWaitTimeSeconds = 1200
   appilog.agent.local.services.loadcontrol.thresh.unsentCIsCount = 30000

   With the parameters configured as above, the system checks the processing time of task results and the unsent CI count every 5 minutes. If there are more than 30,000 unsent CIs in ddm_gw_task_results table and the total processing time of a discovery result takes more than 20 minutes, then the maximum threads for each job is changed to 3 automatically, and the minimal CIs sent by Data Flow Probe each time is reduced to 2000.

   Note  

   • The values set here are only provided as an example. You can customize the configurations to suit your business needs.
   • If neither the number of unsent CIs nor the result processing time reaches the value set in the appilog.agent.local.services.loadcontrol.thresh.resultWaitTimeSeconds or the appilog.agent.local.services.loadcontrol.thresh.unsentCIsCount parameters respectively, the original setting for the maximum threads per job will be applied.
   • If Data Flow Probe is disconnected from UCMDB server, the load control feature would disable itself automatically.

   • When the task results processing performance goes back to normal, the values configured for appilog.agent.local.services.loadcontrol.maxJobThreads and appilog.agent.local.services.loadcontrol.retrievetaskResultsFromDB.minObjects will be automatically changed to the original values configured for normal scenarios.

3. Restart the Data Flow Probe service.

Troubleshooting - Load Control

To troubleshoot the Load Control feature, do the following:

1. Add the following lines to probeMgrLog4j.properties:

   log4j.category.com.hp.ucmdb.discovery.probe.agents.probemgr.adhoctasks=DEBUG, PROCESSOR_LOGFILE
   log4j.category.com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler=DEBUG, PROCESSOR_LOGFILE
   log4j.category.com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter=DEBUG, PROCESSOR_LOGFILE

2. Add the following lines to probeGwLog4j.properties:

   log4j.category.com.hp.ucmdb.discovery.probe.agents.probegw.managementtasks.adhoctasks=DEBUG, PROBE_TASK_RESULT_FILE