[ https://issues.apache.org/jira/browse/JCR-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658156#comment-13658156 ]
Thomas Mueller commented on JCR-3547: ------------------------------------- Sorry for the delay. The patch looks good, I will run the tests and commit it then (to the trunk for now). > 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 > Attachments: GarbageCollector.java.patch, > GC_prevent_concurrent_run_app2.patch, GC_prevent_concurrent_run_final.patch, > GC_prevent_concurrnet_run_app1.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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira