[
https://issues.apache.org/jira/browse/JCR-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank Gupta updated JCR-3731:
--------------------------------
Description:
As per today, when we switch repository from FileDataStore to S3DataStore all
binary files are migrated from local file system to S3Datastore. As per today
this process is single threaded and takes lot of time. For e.g. for 1G intial
content, it takes around 5 min to migrated from ec2 instance to S3.
It can be made faster by migrating content in multi-threaded environment.
was:
As per today, when we switch CRX from ClusterDataStore to S3DataStore all
binary files are migrated from local file system to S3Datastore. As per today
this process is single threaded and takes lot of time. For e.g. for 1G intial
content, it takes around 5 min to migrated from ec2 instance to S3.
It can be made faster by migrating content in multi-threaded environment.
> Multi-threaded migration of binary files from FileSystem to S3 datastore
> -------------------------------------------------------------------------
>
> Key: JCR-3731
> URL: https://issues.apache.org/jira/browse/JCR-3731
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.7.4
> Reporter: Shashank Gupta
> Fix For: 2.7.5
>
>
> As per today, when we switch repository from FileDataStore to S3DataStore all
> binary files are migrated from local file system to S3Datastore. As per today
> this process is single threaded and takes lot of time. For e.g. for 1G intial
> content, it takes around 5 min to migrated from ec2 instance to S3.
> It can be made faster by migrating content in multi-threaded environment.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
