jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-3835) DocumentStore API: specification of timeouts?
Date Tue, 05 Jan 2016 10:02:39 GMT

     [ https://issues.apache.org/jira/browse/OAK-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Julian Reschke resolved OAK-3835.
    Resolution: Duplicate

> DocumentStore API: specification of timeouts?
> ---------------------------------------------
>                 Key: OAK-3835
>                 URL: https://issues.apache.org/jira/browse/OAK-3835
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Julian Reschke
>            Priority: Minor
> 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).

This message was sent by Atlassian JIRA

View raw message