Cisco Bug: CSCuk47925 - Need a strategy for dealing with replication failures
Jan 23, 2016
- Cisco Carrier Routing System
Known Affected Releases
Symptom: This is a problem that has not occured in practice. It is an anticipated issue that while possible is unlikely to occur. Should failures occur while SysDB is performing it's data replication such that the retries are exhasted, the replication will give up an not attempt to replicate the data that it was unable to replicate. However if the standby node goes down (causing replication problems) it will be resynchronized when it reboots, sos in practice the problem of replication failures occuring while the standby card remains operational has not been seen. Conditions: Active and standby RP cards operating normally, new configuration is committed and while the active RP is attempting to replicate the new configuration data to the standby communications failures occur and are sustained long enough that the replication retries are exhasted and the active node gives up attempting to replicate the new configuration to the standby. Now should a failover occur, the standby will not have the current configuration.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases