You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2015/04/09 21:04:14 UTC

[jira] [Updated] (AIRAVATA-1398) Retry incase GSISSH IN/Out handler not able find the data to transfer

     [ https://issues.apache.org/jira/browse/AIRAVATA-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suresh Marru updated AIRAVATA-1398:
-----------------------------------
    Fix Version/s: 0.15 

> Retry incase GSISSH IN/Out handler not able find the data to transfer
> ---------------------------------------------------------------------
>
>                 Key: AIRAVATA-1398
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1398
>             Project: Airavata
>          Issue Type: Improvement
>            Reporter: Raminderjeet Singh
>             Fix For: 0.15 
>
>
> I am seeing cases on Trestles and Lonestar when GFAC output handler is not able to transfer the files. Stdout/error and outputs were produced fine but  may be there was some delay on shared file system to synchronize the files from compute node. Retry with a delay and overall architecture to retry will help improve the job success rate. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)