I can give you a very good example - if you are doing alignment and for some reason need to convert the input file before operating on them, such that you need a complete copy, /tmp may not have enough room. I have had this happen to me running lots of instances of an aligner, temporarily using 100G+ of temp space. I don't see the need to have a "shared" temp space, but I do see the need to be able to tell the tools where you want them to put temp files. John Duddy Sr. Staff Software Engineer Illumina, Inc. 9885 Towne Centre Drive San Diego, CA 92121 Tel: 858-736-3584 E-mail: jduddy@illumina.com -----Original Message----- From: galaxy-dev-bounces@lists.bx.psu.edu [mailto:galaxy-dev-bounces@lists.bx.psu.edu] On Behalf Of Peter Cock Sent: Tuesday, July 26, 2011 8:10 AM To: Galaxy Dev Subject: [galaxy-dev] Cluster setup - shared temporary directory Hi all, I'm reading http://wiki.g2.bx.psu.edu/Admin/Config/Performance/Cluster Could someone expand a little on this section please:
Create a shared temporary directory
Some tools make use of temporary files created on the server, but accessed on the nodes. For this, you'll need to make a directory (galaxy_dist/database/tmp by default) ...
I presume this is talking about the universe_wsgi.ini setting new_file_path = database/tmp (if so, could that be explicit)? I would like to know more about this from the tool author point of view. Could you at least give one example of a tool that uses this temporary folder? As a tool author I am unclear what the purpose is (and it would be a shock if I accidentally use this mapped folder instead of the local temp drive of a node). Thanks, Peter ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/