[jira] [Updated] (OAK-2106) Optimize reads from secondaries

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

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

Marcel Reutegger updated OAK-2106:
----------------------------------
    Description: 
OAK-1645 introduced support for reads from secondaries under certain
conditions. The current implementation checks the _lastRev on a potentially
cached parent document and reads from a secondary if it has not been
modified in the last 6 hours. This timespan is somewhat arbitrary but
reflects the assumption that the replication lag of a secondary shouldn't
be more than 6 hours.

This logic should be optimized to take the actual replication lag into
account. MongoDB provides information about the replication lag with
the command rs.status().


  was:
OAK-1645 introduced support for reads from secondaries under certain
conditions. The current implementation checks the _lastRev on a potentially
cached parent document and reads from a secondary if it has not been
modified in the last 24 hours. This timespan is somewhat arbitrary but
reflects the assumption that the replication lag of a secondary shouldn't
be more than 24 hours.

This logic should be optimized to take the actual replication lag into
account. MongoDB provides information about the replication lag with
the command rs.status().



> Optimize reads from secondaries
> -------------------------------
>
>                 Key: OAK-2106
>                 URL: https://issues.apache.org/jira/browse/OAK-2106
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>              Labels: performance, scalability
>             Fix For: 1.3.0
>
>
> OAK-1645 introduced support for reads from secondaries under certain
> conditions. The current implementation checks the _lastRev on a potentially
> cached parent document and reads from a secondary if it has not been
> modified in the last 6 hours. This timespan is somewhat arbitrary but
> reflects the assumption that the replication lag of a secondary shouldn't
> be more than 6 hours.
> This logic should be optimized to take the actual replication lag into
> account. MongoDB provides information about the replication lag with
> the command rs.status().



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)