Assuming no changes occur to a DAs database, how much traffic would be required to verify that two DAs are synchronized?
A8: DAs do not have some kind of special new synchronization method – they piggy-back on top of NDS synchronization. As long as both DAs have a replica of the Scope Unit object, then they monitor changes there and automatically apply them to the DA cache/table. Also, the SLP Service objects are designed to minimize NDS traffic. Typically only the Default Lifetime attribute is synched (SAs default to re-register every hour, but this could be increased). Even if the server goes down and de-registers the SLP Service, it does not delete the object but sets a flag on the SLP Service Object to mark it as invalid. The SLP DAs in the tree remove the entry from their cache/table, but it remains in NDS for the time being. The server would have to be down for 1-2 days before the object would be deleted from the tree during the nightly DA purge operation (only deleted if the timestamp on the Invalid flag is older than 24 hours).
Related Questions
- What initiatives/changes are likely to occur with GCSE and AS/A- Level given that KS3 is only part of what happens in schools? What is coming next?
- What changes in pedestrian traffic patterns will occur as a result of the construction?
- What changes in vehicle traffic patterns will occur as a result of the construction?
