[
https://issues.apache.org/jira/browse/OAK-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282348#comment-14282348
]
Michael Dürig commented on OAK-2384:
------------------------------------
Tests under real traffic conditions revealed issues with this approach.
Apparently we lose some of the performance optimisations that went into
revision comparison for cached properties. AFICS this interacts badly with the
compaction estimator as in one instance I've seen that one not finishing. I've
also seen this stalling the system in gc.
> SegmentNotFoundException when keeping JCR Value references
> ----------------------------------------------------------
>
> Key: OAK-2384
> URL: https://issues.apache.org/jira/browse/OAK-2384
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Priority: Critical
> Labels: gc
> Fix For: 1.0.10, 1.1.6
>
>
> With OAK-2192 revision gc started to remove segments older than a certain
> threshold. The underlying assumption was that old sessions would call refresh
> (i.e. auto refresh) anyway once they become active again. However, it turns
> out that refreshing a sessions does not affect JCR values as those are
> directly tied to the underlying record. Accessing those values after its
> segment has been gc'ed results in a {{SegmentNotFoundException}}.
> Keeping reference to JCR values is an important use case for Sling's
> {{JcrPropertyMap}}, which is widely used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
