[
https://issues.apache.org/jira/browse/JCR-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169333#comment-14169333
]
Shashank Gupta edited comment on JCR-3817 at 10/13/14 2:36 PM:
---------------------------------------------------------------
* The idea is to update the lastModified asynchronously.
* It keeps a in-memory map which holds all in-progress async touch. No need to
persist it as after restart user needs to run gc again.
* Successful updation of lastModified will remove the entry from map.
* deleteOlderThan doesn't delete a record if its identifier present in
in-progress async touch map.
* Async touch will not work in shared datastore mode and hence it is kept
configurable and by default it is disabled. Set touchAsync=true in
CachingDataStore to enable it.
was (Author: shgupta):
* The idea is to update the lastModified asynchronously.
* It keeps a in-memory map which holds all in-progress async touch. No need to
persist it as after restart user needs to run gc again.
* Successful updation of lastModified will remove the entry from map.
* Async touch will not work in shared datastore mode and hence it is kept
configurable and by default it is disabled. Set touchAsync=true in
CachingDataStore to enable it.
> [jackrabbit-aws-ext] Performance of operation degrades while running DS GC
> --------------------------------------------------------------------------
>
> Key: JCR-3817
> URL: https://issues.apache.org/jira/browse/JCR-3817
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-data
> Affects Versions: 2.9
> Reporter: Shashank Gupta
> Fix For: 2.9.1
>
> Attachments: JCR-3816-3817.patch
>
>
> It is because when GC is running lastModified of each record is updated in S3
> which affects the performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
