[
https://issues.apache.org/jira/browse/OAK-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542010#comment-15542010
]
Amit Jain commented on OAK-3253:
--------------------------------
[~shgu...@adobe.com]FDS assumes reference.key lying in ${path}. you can copy
FDS implementation in CachingFDS.
Yes, but here the reference.key will lie in the fsBackendPath which is
different from the path/getPath() in CachingDataStore. But I think its possible
in a not very clean way to retrieve the fsBackendPath from the properties
object and use it.
> Support caching in FileDataStoreService
> ---------------------------------------
>
> Key: OAK-3253
> URL: https://issues.apache.org/jira/browse/OAK-3253
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
> Affects Versions: 1.3.3
> Reporter: Shashank Gupta
> Assignee: Shashank Gupta
> Priority: Blocker
> Labels: candidate_oak_1_0, candidate_oak_1_2, docs-impacting,
> features, performance
> Fix For: 1.4, 1.3.15
>
> Attachments: OAK-3253.txt,
> org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.config
>
>
> FDS on SAN/NAS storage is not efficient as it involves network call. In OAK.
> indexes are stored SAN/NAS and even idle system does lot of read system
> generated data.
> Enable caching in FDS so the reads are done locally and async upload to
> SAN/NAS
> See [previous
> discussions|https://issues.apache.org/jira/browse/OAK-3005?focusedCommentId=14700801&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14700801]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
