[
https://issues.apache.org/jira/browse/OAK-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032122#comment-14032122
]
Jukka Zitting commented on OAK-1877:
------------------------------------
There was a related problem in that the indexing status properties written by
the async indexer would end up triggering the next async indexing iteration,
thus still causing a new checkpoint to be created once every five seconds even
if no other changes were committed between successive async indexer
invocations. I fixed that in revision 1602796 (and 1602797), and merged the
changes to the 1.0 branch in revision 1602798.
> Hourly async reindexing on an idle instance
> -------------------------------------------
>
> Key: OAK-1877
> URL: https://issues.apache.org/jira/browse/OAK-1877
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Critical
> Fix For: 1.0.1, 1.1
>
>
> OAK-1292 introduced the following interesting but not very nice behavior:
> On an idle system with no changes for an extended amount of time, the
> OAK-1292 change blocks the async indexer from updating the reference to the
> last indexed checkpoint. After one hour (the default checkpoint lifetime),
> the referenced checkpoint will expire, and the indexer will fall back to full
> reindexing.
> The result of this behavior is that once every hour, the size of an idle
> instance will grow with dozens or hundreds of megabytes of new index data
> generated by reindexing. Older index data becomes garbage, but the compaction
> code from OAK-1804 is needed to make it collectable. A better solution would
> be to prevent the reindexing from happening in the first place.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
