[Swift-devel] [Bug 127] New: proxy expiration whilst jobs are running through GRAM4

bugzilla-daemon at mcs.anl.gov bugzilla-daemon at mcs.anl.gov
Mon Mar 31 05:22:26 CDT 2008


http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=127

           Summary: proxy expiration whilst jobs are running through GRAM4
           Product: Swift
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: General
        AssignedTo: nobody at mcs.anl.gov
        ReportedBy: benc at hawaga.org.uk
                CC: benc at hawaga.org.uk, swift-devel at ci.uchicago.edu


If the user proxy expires whilst a job is running from Swift through GRAM4,
that job will hang in the swift runtime.

This is reproducable by running a 5 minutes sleep job with a 2 minute proxy. 

I think (though I haven't looked at gram server side logs to check) what is
happening here is that status notifications cannot be delivered because of the
expired credential; and the job then sits forever waiting for the notification
that will never come.                                              

If so, then probably it would be better to refresh the credential if possible;
and fail the job if we know that we cannot get notifications because the local
proxy has expired.


-- 
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



More information about the Swift-devel mailing list