[
https://issues.apache.org/jira/browse/OAK-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783291#comment-13783291
]
Michael Dürig commented on OAK-1060:
------------------------------------
In [the same chat |
https://issues.apache.org/jira/browse/OAK-1055?focusedCommentId=13783287&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13783287]
we also discussed that splitting the single
{{PostCommitHook.contentChanged()}} method up into three separate methods as
proposed in OAK-775 helps with polling for external events without the
problematic race.
> Periodically poll for external events
> -------------------------------------
>
> Key: OAK-1060
> URL: https://issues.apache.org/jira/browse/OAK-1060
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Michael Dürig
> Priority: Minor
>
> Currently external events are only reported along with local changes. That
> is, when local changes are persisted external changes are detected and
> reported along with the local changes. This might cause external events to be
> delayed indefinitely on cluster nodes without writes.
> We might want to implement a solution that regularly polls for external
> events.
> See OAK-1055 for why a previous implementation didn't work.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
