Cisco Cisco Prime Network Registrar 8.3 Troubleshooting Guide



#replmon.slave.connect.error = replmon_slave_connect_error_callout.sh 
 
# The monitor reconnected to the Passive Master (or slave) server after a prior disconnect 
#replmon.slave.reconnected = replmon_slave_reconnect_callout.sh 
 
# The monitor detected that the Passive Master has begun to lag behind the  
# Active Master beyond the lagNotificationThreshold defined in the 
# replication monitor's configuration file. 
#replmon.slave.lag.start = replmon_slave_lag_start_callout.sh 
 
# The monitor detected that the Passive Master has completely resynchronized with the 
master 
# after a prior notified lag. 
#replmon.slave.resynched = replmon_slave_resynched_callout.sh 

You can set up the Replication Monitor to purge binary logs that have already been read by 

the slave server, as well as control the interval at which it checks to see whether there are logs 
to purge. Set up the following parameters in the 

mysql_replication_monitor.properties

 file. 

  

When set to True, instructs the Active Master to purge any binary logs that have already been 

read by the slave. It purges logs up to the penultimate log used by the slave. 
For example, if the slave is current to 

mysql-bin.00020

, the purge log removes all files 

except for 

mysql-bin.00020

 and 

mysql-bin.00019

. 

  

By default, instructs the Replication Monitor to check if it can purge logs every 300000 
milliseconds, which is the equivalent of 300 seconds (or five minutes).