[Swift-devel] Persistent coasters running one job per worker

[Mihael Hategan]

Ah!

If the workers connect before the client does, then jobsPerNode does not
make it to the coaster service.

I'll think about this. In the mean time, you could have the workers
started after the client sends its first job to the service.

I'm thinking that maybe jobsPerNode should be a setting that the workers
themselves could be started with.

On Tue, 2011-08-09 at 14:09 -0500, Ketan Maheshwari wrote:
> I do not see any recent log in ~/.globus/coasters. The stdout/err of
> the coaster service run is in the attached service.log and the
> coaster.log is in the attached swift.log. 
> 
> 
> 
> 
> On Tue, Aug 9, 2011 at 1:59 PM, Mihael Hategan <hategan at mcs.anl.gov>
> wrote:
>         but but but I checked this, and it worked fine...
>         
>         Can you also post the coasters log (on the machine the coaster
>         service
>         is on, in ~/.globus/coasters)?
>         
>         
>         On Tue, 2011-08-09 at 13:47 -0500, Ketan Maheshwari wrote:
>         > Mihael,
>         >
>         >
>         > I was discussing this with Justin and we thought you could
>         help:
>         >
>         >
>         > I am observing that persistent coasters are running one job
>         per worker
>         > as opposed to the number specified in jobspernode (I also
>         tried
>         > nodegranularity) on sites.xml.
>         >
>         >
>         > Attaching the log, and the sites.xml for the run. Swift is
>         0.93 (Swift
>         > svn swift-r4968 cog-r3225).
>         >
>         >
>         > The script is Mike's catsnsleep that sleeps for 20s with
>         n=10.
>         >
>         > --
>         > Ketan
>         >
>         >
>         >
>         
>         
>         
> 
> 
> 
> -- 
> Ketan
> 
> 
>