[Swift-user] Running coasters on a bag of workstations

[David Kelly]

Carsen,

When you set WORKER_LOCATION to a non-shared directory, you need to enable coaster provider staging. To do this, add a line to your coaster-service.conf that says:

export SHARED_FILESYSTEM=no

When you run start-coaster-service the next time, a file called 'cf' will be created. Then run swift with something like this:
swift -sites.file sites.xml -tc.file tc.data -config cf myscript.swift

I think this should do the trick, but please let me know if you run into anything else. I'll try to update the documentation to make this more clear.

Regards,
David

----- Original Message -----
> From: "Carsen Berger" <clberger at uchicago.edu>
> To: swift-user at ci.uchicago.edu
> Sent: Saturday, May 19, 2012 4:17:03 PM
> Subject: [Swift-user] Running coasters on a bag of workstations
> Hi all,
> 
> I'm trying to run coasters on a collection of commodity machines and
> I'm running into some issues. The machines all share a common /home
> directory on a NFS file system, so to give the coaster workers local
> storage, I decided to set the WORKER_LOCATION directory to the local
> /var/tmp on each machine.
> 
> Running start-coaster-service installs worker.pl in /var/tmp just
> fine, but then when we try to run a swift script it spits out a slew
> of "No such file or directory" errors for all the files that the
> worker is supposed to create. It seems as if coasters cannot write to
> /var/tmp for whatever reason. Has anyone encountered a problem like
> this before?
> 
> Note that setting WORKER_LOCATION to a directory in /home circumvents
> this problem, but that solution won't work because we need a directory
> that is local to each machine.
> 
> Thank you,
> Carsen Berger
> 
> _______________________________________________
> Swift-user mailing list
> Swift-user at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-user