jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1877) Hourly async reindexing on an idle instance
Date Thu, 12 Jun 2014 15:48:01 GMT

    [ https://issues.apache.org/jira/browse/OAK-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029280#comment-14029280

Alex Parvulescu commented on OAK-1877:

I added a null check surrounding the release call. This prevents a NPE and complies with the
api contract of never passing a null value. (trunk rev 1602207, branch 1.0 rev 1602211).

> 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

View raw message