This page was last edited on February 21, 2017, at 05:45.
Comments or questions about this documentation? Contact us for support!
When there are updates in the Configuration Database, then Feature Server synchronizes the following objects.
SIP Feature Server synchronization with Configuration Database consists of the following three functional facilities:
Initial import synchronization occurs during the first time the Master Feature Server is started. During this synchronization, switch objects and tenant objects are imported from the Configuration Database. To avoid repeating the import, Feature Server saves/retains initial import flags in Cassandra Database. After the check, Feature Server imports when required.
During real-time synchronization, Feature Server dynamically synchronizes Cassandra database with updates from the Configuration Database.
History log retrieval synchronization occurs when Feature Server is disconnected and then reconnected to the Configuration Database. During this process, Cassandra is updated with all the changes in the Configuration Database during the time when Feature Server was disconnected. If the history log is lost owing to a Feature Server outage, reimport mechanism is triggered automatically. For more details on reimporting, see Reimporting Configuration Data.