You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2014/06/09 16:44:02 UTC

[jira] [Resolved] (OAK-1877) Hourly async reindexing on an idle instance

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

Jukka Zitting resolved OAK-1877.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1
                   1.0.1

I ran a test with this change overnight, and the result is that an idle (AEM6) repository only grows about 1MB per hour (haven't yet figured out where that growth is coming from). That is two orders of magnitude less than before with no regressions I can find, so I merged the fix to the 1.0 branch in revision 1601396. I think we can consider this issue resolved.

> 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)