[
https://issues.apache.org/jira/browse/OAK-11766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved OAK-11766.
----------------------------------
Resolution: Fixed
trunk:
[963dc6425d|https://github.com/apache/jackrabbit-oak/commit/963dc6425d7a819c6762ce92a064ac0e6a69fa3f]
[7c96ca531a|https://github.com/apache/jackrabbit-oak/commit/7c96ca531a1f91c10423ad311a04aa28ace5bc8b]
[201c1c894f|https://github.com/apache/jackrabbit-oak/commit/201c1c894f233b16ed0559011fee32d21b0ce257]
> Write Throttling Mechanism - Session.save() delay
> -------------------------------------------------
>
> Key: OAK-11766
> URL: https://issues.apache.org/jira/browse/OAK-11766
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Thomas Mueller
> Priority: Major
> Labels: indexing
> Fix For: 1.82.0
>
>
> Asynchronous index updates can fall behind writes in the following cases:
> * When using the document node store (it is theoretically also possible with
> other node stores, but I didn't see the behavior with others), and
> * if many threads concurrently write to the repository (eg. using POST
> servlets), and
> * if multiple cluster nodes concurrently write, and
> * if there are many indexes that are relatively expensive.
> The challenge is that there is only one thread, per async lane, that can
> update the indexes. What I have seen is that this indexing lane can fall
> behind, and possibly (if write load persists for multiple hours) this
> indexing lane never recovers within a reasonable time.
> To resolve the problem, I propose that we introduce a delay mechanism to
> configure delays in Session.save() calls.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
