-
Type:
Improvement
-
Status: Dev backlog
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 4.0.0
-
Fix Version/s: None
-
Component/s: devops, replication
-
Labels:None
When a DS stops without sending a replica offline message, it blocks computing of the change number on the replication servers. Various reasons exist for a DS to stop abruptly:
- kill -9
- linux OOM killer
- when the machine where a DS is installed dies and is irrecoverable
- etc.
To unblock computing of the change number, we could add a subcommand to dsreplication that would (in the end) send a ReplicaOfflineMsg on behalf of the DS that is gone. This will tell the replication servers to not wait for it when computing change numbers.
- depends on
-
OPENDJ-5051 Simplify handling of replica offline messages in the changelog
-
- Done
-
- is related to
-
OPENDJ-4587 Replication: Medium consistency point frozen when a DS+RS is unconfigured or a DS+RS is stopped
-
- Done
-
-
OPENDJ-6682 Divergences in replication after upgrade from 2.6.4: entry missing in the changelog
-
- Done
-
- is required by
-
OPENDJ-4185 Changelog not populated with new changes if an RS+DS goes down and replication fails to catch up when it's restarted
-
- Dev backlog
-
-
OPENDJ-3984 Add dsreplication command to remove an offline replica from a topology
-
- Done
-
- relates to
-
OPENDJ-3985 Provide a way to remove obsolete replica IDs from the databases
-
- Done
-