2002-08-20 23:54:17 +00:00
|
|
|
<title>Remote File Access</title>
|
|
|
|
|
<body bgcolor=ffffff>
|
|
|
|
|
<h2>Remote File Access</h2>
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-08-20 23:54:17 +00:00
|
|
|
Output files can be designated as sticky but not upload-when-present.
|
2002-08-19 18:43:10 +00:00
|
|
|
Sometimes this is done because the file will be
|
2002-07-29 19:01:38 +00:00
|
|
|
used as an input for a later workunit; it may also be done to spread
|
|
|
|
|
large output data across participant disks, in cases where the data may
|
|
|
|
|
be too large to store on the project back-end.
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-08-19 18:43:10 +00:00
|
|
|
To access such a file, the back end inserts a <b>file access
|
|
|
|
|
request</b> in the database.
|
|
|
|
|
This specifies a file and a data-server URL.
|
|
|
|
|
When a host storing the file contacts the scheduling server (which
|
2002-07-29 19:01:38 +00:00
|
|
|
may not happen for a while) the scheduling server forwards the file
|
2002-08-19 18:43:10 +00:00
|
|
|
access request.
|
|
|
|
|
The host confirms the file transfer when it is
|
2002-07-29 19:01:38 +00:00
|
|
|
completed; the back-end must poll for this event.
|
