[ https://issues.apache.org/jira/browse/OAK-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138662#comment-14138662 ]
Chetan Mehrotra commented on OAK-2106: -------------------------------------- OAK-1750 is somewhat related to that and proposes an approach we can take to determine the replication lag in a more accurate way > 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 > > 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(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)