[
https://issues.apache.org/jira/browse/AIRAVATA-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17535146#comment-17535146
]
Eroma edited comment on AIRAVATA-3586 at 5/12/22 12:17 AM:
-----------------------------------------------------------
A global configuration exists in the production from Helix only directories
less than 20 GB is brought back to Airavata/Helix side. Currently, this is set
at global level, and if we want we can set this up in participant properties.
(participant/airavata-server.properties.j2)
max.archive.size=<total bytes>
Test in django.seagrid.org
was (Author: eroma_a):
A global configuration exists in the production from Helix only directories
less than 20 GB is brought back to Airavata/Helix side. Currently, this is set
at global level, and if we want we can set this up in participant properties.
(participant/airavata-server.properties.j2)
max.archive.size=<total bytes>
> Restrict ARCHIVE directory unzip if its above a configured accepted size.
> -------------------------------------------------------------------------
>
> Key: AIRAVATA-3586
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3586
> Project: Airavata
> Issue Type: New Feature
> Components: Django Portal
> Reporter: Eroma
> Assignee: Marcus Christie
> Priority: Major
>
> Currently in applications we can configure the ARCHIVE. to be brought back.
> When it is on Django Portal server, the ARCHIVE is unzipped so the user could
> download the files, etc
> Sometimes the ARCHIVE could have thousands of files or can contain very large
> files. In such situations unarchiving is heavy on the storage and if it has
> thousands of files replica catalog would be getting records created for each
> file.
> Hence, with the new proposed implementation, if the ARCHIVE is above a
> configured size, then it will not be unzipped, will be presented as a single
> zip file. User can download and unzip in the local machine.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
