[ https://issues.apache.org/jira/browse/OAK-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745425#comment-14745425 ]
Michael Dürig commented on OAK-3372: ------------------------------------ There is not clustering option for the segment node store (yet). However see {{SegmentNodeStore#refreshHead}}, which might trigger "external" events for some changes. This is most likely also the point where true external changes would get pulled in from if if we had/once we have the clustering. > Collapsing external events in BackgroundObserver even before queue is full > leads to JournalEntry not getting used > ----------------------------------------------------------------------------------------------------------------- > > Key: OAK-3372 > URL: https://issues.apache.org/jira/browse/OAK-3372 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core > Affects Versions: 1.3.5 > Reporter: Vikas Saurabh > Labels: resilience > > BackgroundObserver currently merges external events if the last one in queue > is also an external event. This leads to diff being done for a revision pair > which is different from the ones pushed actively into cache during backgroud > read (using JournalEntry) i.e. diff queries for {{diff("/a/b", rA, rC)}} > while background read had pushed results of {{diff("/a/b", rA, rB)}} and > {{diff("/a/b", rB, rC)}}. > (cc [~mreutegg], [~egli], [~chetanm], [~mduerig]) -- This message was sent by Atlassian JIRA (v6.3.4#6332)