You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2017/10/18 12:52:00 UTC
[jira] [Commented] (JCR-3547) Datastore GC doesn't reset
updateModifiedDateOnAccess on datastore
[ https://issues.apache.org/jira/browse/JCR-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209276#comment-16209276 ]
Julian Reschke commented on JCR-3547:
-------------------------------------
trunk: [r1482732|http://svn.apache.org/r1482732]
> Datastore GC doesn't reset updateModifiedDateOnAccess on datastore
> ------------------------------------------------------------------
>
> Key: JCR-3547
> URL: https://issues.apache.org/jira/browse/JCR-3547
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.4, 2.5
> Reporter: Shashank Gupta
> Assignee: Thomas Mueller
> Fix For: 2.7.1
>
> Attachments: GC_prevent_concurrent_run_app2.patch, GC_prevent_concurrent_run_final.patch, GC_prevent_concurrnet_run_app1.patch, GarbageCollector.java.patch
>
>
> In mark phase, GC updates store.updateModifiedDateOnAccess with current time, so that datastore updates record’s lastModified timestamp upon subsequent read/scan.
> But GC doesn't reset it to 0. So even after GC completes, datastore will continue updating lastModified timestamp on read invocations and it will have performance impact.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)