[Swift-user] passive worker connection to service.
Allan Espinosa
aespinosa at cs.uchicago.edu
Thu Oct 21 19:17:34 CDT 2010
I see. Now this reduce my concerns to just the persistence of the
coaster service across runs (other post).
Thanks!
-Allan
2010/10/21 Mihael Hategan <hategan at mcs.anl.gov>:
> On Thu, 2010-10-21 at 17:53 -0500, Allan Espinosa wrote:
>> Can you guys confirm this for me?
>>
>> Does the passive worker client only initiates one (1) register request
>> to the service? If so, then that worker is as good as gone when the
>> service shuts down and gets restarted? Or will it register again to
>> that service?
>>
>
> The worker is as good as gone when the service shuts down.
>
> That's why you use a persistent service when you want to persist workers
> between different runs. The passive worker is not meant to address that.
> Instead it is meant to override the automatic worker submission in order
> to allow that to work in environments for which there is no provider.
>
--
Allan M. Espinosa <http://amespinosa.wordpress.com>
PhD student, Computer Science
University of Chicago <http://people.cs.uchicago.edu/~aespinosa>
More information about the Swift-user
mailing list