[Swift-devel] midway jobs not directed to right site

[Ketan Maheshwari]

Thanks Mihael! Works after turning off provider staging and setting
filesystem provider in each of the queue pools.


On Sat, Apr 20, 2013 at 12:59 AM, Mihael Hategan <hategan at mcs.anl.gov>wrote:

> They probably go to the right site, but all of those sites point to
> whatever coaster service runs on localhost of which there is only one
> (once one is started, whenever you try to run a coaster job on
> localhost, the already started service will be used).
>
> So you might want to change the last site to use the local provider
> instead.
>
> Mihael
>
> On Fri, 2013-04-19 at 20:32 -0500, Ketan Maheshwari wrote:
> > Hi,
> >
> > I am trying to run a script where some lightweight jobs were destined to
> > run on localhost while others were to run on sandyb/westmere queues in
> > midway.
> >
> > I do this by putting the right handle before the app name in my tc. The
> > corresponding pool entry being in the sites.xml
> >
> > However, it looks like all the jobs in the script are running on
> localhost
> > instead.
> >
> > When I comment out the localhost part from the sies.xml and the script, I
> > correctly get them to run on sandyb/westmere queues.
> >
> > In order to verify this, I tried to run a Swift script with three jobs
> each
> > destined to westmere, sandyb and localhost echoing a message and printing
> > the hostname. I do find the same behavior in this case too. Jobs were all
> > running on localhost and none on the queues.
> >
> > See the above mentioned example bundle with logs and config files here:
> >
> > http://www.mcs.anl.gov/~ketan/sites_exp.tgz
> >
> > Should run straightaway with ./run.midway and . in PATH.
> >
> >
> > Feature or bug?
> > Hi,
> >
> >
> > I am trying to run a script where some lightweight jobs were destined
> > to run on localhost while others were to run on sandyb/westmere queues
> > in midway.
> >
> >
> > I do this by putting the right handle before the app name in my tc.
> > The corresponding pool entry being in the sites.xml
> >
> >
> > However, it looks like all the jobs in the script are running on
> > localhost instead.
> >
> >
> > When I comment out the localhost part from the sies.xml and the
> > script, I correctly get them to run on sandyb/westmere queues.
> >
> >
> > In order to verify this, I tried to run a Swift script with three jobs
> > each destined to westmere, sandyb and localhost echoing a message and
> > printing the hostname. I do find the same behavior in this case too.
> > Jobs were all running on localhost and none on the queues.
> >
> >
> > See the above mentioned example bundle with logs and config files
> > here:
> >
> >
> > http://www.mcs.anl.gov/~ketan/sites_exp.tgz
> >
> >
> >
> > Should run straightaway with ./run.midway and . in PATH.
> >
> >
> >
> >
> > Feature or bug?
> > --
> > Ketan
> >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
>
>


-- 
Ketan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20130420/6d9e683d/attachment.html>