I am experiencing a delay in our database tables that are being logged by a transaction group when our redundancy back up switches back to the master. There does not seem to be any delay when the master goes down and the backup node takes over. I am assuming this is because the backup is set to warm. If I am correct is there a way to make the master wait till it is reading values from all the tags before becoming active? or at least delay the fail over back to the master?
my group is set to log every 5 minutes. when i stop the Ignition service on the master node the backup then takes over. I wait for the backup node to write a record to the table, which is within 5 minutes of the master going down. Then i start the service backup on the master, but a record does not seem to get written to the table for at least 15 minutes. I am losing a transaction or two.