Details
Description
Currently the lease mechanism in DocumentNodeStore/mongoMk is based on the assumption that the clocks are in perfect sync between all nodes of the cluster. The lease is valid for 60sec with a timeout of 30sec. If clocks are off by too much, and background operations happen to take couple seconds, you run the risk of timing out a lease. So introducing a check which WARNs if the clocks in a cluster are off by too much (1st threshold, eg 5sec?) would help increase awareness. Further drastic measure could be to prevent a startup of Oak at all if the difference is for example higher than a 2nd threshold (optional I guess, but could be 20sec?).
Attachments
Attachments
Issue Links
- blocks
-
OAK-2844 Introducing a simple document-based discovery-light service (to circumvent documentMk's eventual consistency delays)
- Closed
-
SLING-4603 discovery.oak: oak-based discovery implementation
- Closed
-
OAK-2739 take appropriate action when lease cannot be renewed (in time)
- Closed
- is related to
-
OAK-4984 Server time unavailable with authenticated connection to MongoDB
- Closed
-
OAK-3623 backport DocumentStore time diff API back
- Closed
- relates to
-
OAK-2681 Update lease without holding lock
- Closed
-
OAK-3238 fine tune clock-sync check vs lease-check settings
- Closed