[OAK-3835] DocumentStore API: specification of timeouts?

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Component/s: documentmk
• Assignee: Unassigned
• Reporter: Julian Reschke
• Created: 05/Jan/16 09:59
• Updated: 01/Sep/16 09:29
• Resolved: 05/Jan/16 10:01

Description

With the latest changes to the lease checks, failures to renew the lease are now much more visible (which is good).

That said, we've seen cases in testing where the actual database operation updating the CLUSTER_NODES entry took minutes, eventually timing out. This makes problem analysis harder than it should me.

Optimally, the API would allow the caller to set a timeout, after which the operation should be aborted. This would make the system fail more deterministically.

Alternatively, a DS implementation could make assumptions about timeouts based on the Collection it operates on (but this fails like a hack to me).

Issue Links

• duplicates: OAK-3822 DocumentStore query API should allow specifying a timeout for queries
• is related to: OAK-4739 lease: immediate renew after long renew call