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] [Created] (OAK-3835) DocumentStore API: specification of timeouts?
Date Tue, 05 Jan 2016 09:59:39 GMT
Julian Reschke created OAK-3835:

             Summary: 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

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

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