Configuring a cell to generate an out-of-sync event


Supported with 11.3.03 and later

The out-of-sync event for cell databases is supported only with:

  • TrueSight Presentation Server version 11.3.03 and later
  • TrueSight Infrastructure Management server version 11.3.03 and later

In an application high availability deployment of TrueSight Infrastructure Management, the cell databases (MCDBs) may go out of sync in the following scenarios:

  • When the nodes recover from a split-brain condition.
  • When the secondary server is down for a long time and the Infrastructure Management processes on the primary server have been restarted multiple times.

To proactively check the status of cell databases in the high-availability mode, you can configure a few class parameters in the pronet.conf that will periodically check the MCDB data of the primary and the secondary cells. The cell generates an OK event if the databases are in sync, and a Critical event if they are out of sync.

To configure the cell to generate MCDB sync status events, do the following:

  1. Go to the <Infrastructure Management server Install Directory>\pw\custom\conf\ directory and open the pronet.conf file using a text editor.

  2. (Optional) Add this property and set to false if you do not want the MCDB sync status to be computed. By default, this property is set to true.

    pronet.agent_controller.cell.mcdb.mismatch.check.enabled=true
  3. (Optional) Modify this property to change the time interval at which the MCDB sync status is computed. By default, the MCDB sync status is computed once every 70 minutes or 4200 seconds. If you change this time interval, ensure that the time interval is greater than 4200 seconds.

    pronet.agent_controller.cell.mcdb.mismatch.check.interval.seconds=4200
  4. (Optional) Modify this property to change the maximum percentage deviation of data and event count between the primary and the secondary cell. By default, this property is set to 1%.

    pronet.agent_controller.cell.mcdb.mismatch.deviation.max.percent=1
  5. (Optional) Modify this property, if you want to modify the time at which the MCDB mismatch deviation percentage is computed. By default, while computing the MCDB mismatch deviation percentage, the system fetches 1 hour prior event and data count that is current time – 3600 seconds (by default, delta.seconds is set to 3600 seconds). 

    pronet.agent_controller.cell.mcdb.mismatch.delta.seconds=3600
  6. (Optional)  Modify this property to change the delay interval (in seconds) after which the MCDB sync status process starts after the agent controller process is started. By default, it is set to 4200 seconds.

    #Default value 
    pronet.agent_controller.cell.mcdb.mismatch.delay.startup.seconds=4200
  7. (Optional) Modify this property to change the number of retries for which the MCDB sync status is computed repeatedly if the MCDB sync status fails. By default, this value is set to 3. If the MCDB sync status fails for the defined number of retries, then an MCDB mismatch event is triggered. 

    pronet.agent_controller.cell.mcdb.mismatch.detect.alarmafter.n.times=3
  8. Save and close the pronet.conf file. 
  9. Restart the Infrastructure Management Server.

Related topic

To troubleshoot the MCDB out of sync status, see  Troubleshooting an Infrastructure Management high-availability deployment. Open link

Was this page helpful? Yes No Submitting... Thank you

Comments