You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2018/02/28 19:02:01 UTC
[jira] [Reopened] (AIRAVATA-2620) Force post processing
functionality
[ https://issues.apache.org/jira/browse/AIRAVATA-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eroma reopened AIRAVATA-2620:
-----------------------------
Reopening as ARCHIVE doesn't work when FORCE PROCESSING. Empty ARCHIVE directory get created, transferred. Some of the exceptions thrown at individual server level are not brought back and displayed to the user. Few improvements to do when it comes to notifying the user at the end of FORCE PROCESSING, file transfers and when an incorrect experiment ID or gateway ID is provided by the user.
> Force post processing functionality
> ------------------------------------
>
> Key: AIRAVATA-2620
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2620
> Project: Airavata
> Issue Type: Improvement
> Affects Versions: 0.16
> Reporter: Suresh Marru
> Assignee: Dimuthu Upeksha
> Priority: Major
> Fix For: 0.17
>
>
> Due to current limitations of only relying on email for job monitoring, the post-processing sometimes has inherent delays. Ultrascan science gateway would like to have a capability in airavata to request forcing of post processing. This will be used when clients have out of band knowledge about job completion (for example through code instrumented UDP messages) and would like Airavata to force staging of output files.
> This improvement has to be carefully added so existing life cycle of an experiment is not hampred.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)