| Exit Print View | |
Sun OpenDS Standard Edition 2.0 Architectural Reference |
|
|
|
The Directory Server Access Control Model
Understanding the Directory Server Schema
Understanding Directory Server Plug-Ins
Overview of the Directory Server Replication Architecture
Basic Replication Architecture
Directory Server Change Processing
Historical Information and Conflict Resolution
What is a Replication Conflict?
Purging Historical Information
Schema Replication Architecture
Replication Status Definitions
Full Update Status and Bad Generation ID Status
Replication Groups in a Multi-Data Center Deployment
Safe Read Mode and Replication Groups
Assured Replication Connection Algorithm
Assured Replication and Replication Status
Assured Replication Monitoring
A directory server that is slow in replaying changes is assigned a DEGRADED_STATUS. The stage at which the server is regarded as “too slow” is defined by the degraded status threshold and is configurable, based on the number of updates queued in the replication server for that directory server.
When the degraded status threshold is reached, the directory server assumes a degraded status and is considered to be unable to send acknowledgments in time. A server with this status can have an impact on assured replication, as replication servers no longer wait for an acknowledgment from this server before returning their own acknowledgments.
|
|