[ 
https://issues.apache.org/jira/browse/OAK-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-1877.
----------------------------------

    Resolution: Fixed

changed the patch a bit, talked to Jukka and we've decided to keep the latest 
checkpoint and simply update the ref to it, instead of keeping the old one 
(good for gc reasons too).

Marking as fixed, on trunk with rev http://svn.apache.org/r1602872, on 1.0 with 
rev 1602874.

> 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
>
>         Attachments: updates-without-indexed-changes.patch
>
>
> 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)

Reply via email to