What are Obituaries#Since eDirectory is a Distributed Data Store, each server receives updated information through synchronization. Since all the servers in the replica ring are Eventual consistency, the server may not hold the same information at a given time. As a result, each server holds on to the old information until all the other servers receive the updates. eDirectory uses NDS Obituaries to keep track of this type of information and more.
NDS Obituaries are created when an eDirectory object is:#obituary itself is an attribute of the object on which the change took place. The reason for an obituary attribute is created is to maintain database consistency between real copies of the object and NDS External References of the changed object. partition, if the ModifyTimestamp of the OBIT_PURGEABLE obituary is OLDER then the timestamp value recorded for the Purge Vector attribute, for each server Replica number in the Replica List as used in the Transitive Vector. The PurgeVector will only be updated if the partition has a successful sync cycle. The purpose of PurgeVector attribute is to prevent NDS Obituaries from being purged before all Edirectory Replicas have been OBIT_NOTIFIED. The values in the attribute are recorded per Replica number, therefore per server in the Replica List. Ndsrepair checks and fixes theNDS Obituaries values.
Three of these types are monitored. Data is displayed for three different types of obituaries:
- OBIT_DEAD: created when an object is deleted.
- OBIT_NEWRDN: created when an object is renamed.
- OBIT_MOVED: created when an object is moved from one location to another.
There are 12 different distinct combinations for a given NDS Obituaries#NDS Obituary States and monitored NDS Obituaries Types generate the distinct combinations:
NDS Obituaries Process Optimization#Prior EDirectory 188.8.131.52 (20801.46) had two redundant methods of processing obituaries:
- DRLs (Distributed Reference Links). The DRL method has been removed eliminating these unnecessary cycles.
Prior to EDirectory 184.108.40.206 (20801.46), the NDS Obituaries process would not run on a partition if the server was currently outbounding changes for that partition to other servers. This would cause NDS Obituaries for that partition to be delayed. In a busy environment with hundreds of changes per second this could lead to Change Cache buildup. Now the obituary process can run in parallel with outbound synchronization thereby reducing NDS Obituaries processing delays.
More Information#There might be more information for this subject on one of the following:
- BACKLINK Obituary
- EDirectory Monitor Entry
- EDirectory Synchronization
- Flat Cleaner
- INHIBIT_MOVE Obituary
- MOVE Sub-Tree Obituary
- MOVED From Obituary
- NDS External References
- NDS Obituaries
- NDS Obituaries Classification
- NDS Obituaries Type
- NDS Obituary State
- NDS Secondary Obituaries
- NDS Unknow Entries
- NDSTRACE Examples
- OLD RDN Obituary
- PURGE ALL Obituary
- RESTORED Obituary
- Simple Health Check
- Tree_new_RDN Obituary
- Tree_old_RDN Obituary
- Used_By Obituary