[Swift-devel] Coaster Task Submission Stalling

Mihael Hategan hategan at mcs.anl.gov
Thu Sep 11 12:37:32 CDT 2014


On Thu, 2014-09-11 at 10:30 -0500, Tim Armstrong wrote:
> This all sounds great.
> 
> Just to check that I've understood correctly, from the client's point of
> view:
> * The per-client settings behave the same if -shared is not provided.

Yes.

> * Per-client settings are ignored if -shared is provided

Yes. You need to send the init command though to get a config id.

> 
> I had one question:
> * Do automatically allocated workers work with per-client settings?

It was supposed to work before and it is now (according to my testing).

>   I understand there were some issues related to sharing workers between
> clients.  Was the solution to have separate worker pools, or is this just
> not supported?

With -shared there is one worker pool and one set of settings. Without
-shared, each client gets a worker pool (with its own settings). The
issue wasn't conceptual. Just poor code-writing on my part.

Mihael





More information about the Swift-devel mailing list