Scratch storage serves as a temporary location for large data sets that ideally reside in an archive space like
Economy storage, to be transferred to when compute processes are applied to them. Data in
Scratch are typically then deleted automatically after certain timeframes when they are no longer needed. Intermediate data that is generated can be saved in
Scratch as well, and then the final data resulting from the compute process can be written to
Fast storage for the researcher. This allows large data to be archived in
Economy storage, accessed by HPC when it is temporarily housed in
Scratch and only the (typically smaller) resulting data are written to the more accessible, but more costly
Why is Scratch Different?
The scratch file system is maintained by SciComp for temporary storage of research data during active analysis. This is a large, high-performance storage system. It is not designed to be as available or as robust as the home or fast file systems meant for long term data storage (these features were traded for lower cost and greater volume). Data here is purged when unused for some amount of time (10, 30, and 90 days depending on the location).
Data on this platform is not backed up. This storage is not appropriate for storing the primary or only copy of any data.
Similar to the Fast File system above, the scratch file system is available on the path
/fh/scratch on SciComp supported Linux systems,
\\center.fhcrc.org\fh\scratch on Windows, and
smb://center.fhcrc.org/fh/scratch on Mac.
There is no charge to the investigator for data stored here.
Why use Scratch Storage for temporary data?
In bioinformatics workflows we are often using pipelines with many execution steps. Each of these steps can create a large amount of temporary data, for example extracting information from genomics data (BAM files). This data often needs to be kept for a short period of time to allow for quality assurance.
Informaticians often do not delete this data after this step because they are already off to the next task. Even worse, if temporary data is created in a standard file system such as
Fast storage it will be picked up by the backup system and copied to the cloud the next night. If data is frequently created and deleted the backup data can grow to 5 or even 10 times the size of the primary data which is an enormous waste. To prevent this waste every informatician or Data Scientist working with large datasets should use
Scratch storage as part of their routine.
For this purpose we have a scratch file systems attached to the
Koshu clusters. There is a different scratch file system mounted on each cluster. Using a scratch resource has several advantages:
- The scratch file system is free of charge
- It is the most performant storage system connected to
- You do not have to clean up your temporary data because the system does it for you
- It reduces Fred Hutch storage expenses because the data is not backed up to the cloud.
Note: Even if you delete data from
Faststorage one day after creation it will be kept in the backup system for a long time.
Types of Scratch Storage Available
On Gizmo there are three forms of scratch space available: “node local job scratch”, “network job scratch” and “network persistent scratch”. The “network job scratch” and “node local” scratch directories and their contents exist only for the duration of the job- when the job exits, the directory and its contents are removed.
For more persistent scratch space, please see the persistent Scratch section.
Node Local Job Scratch
There are varying volumes of local storage depending on node configuration and utilization by other jobs. If you require a large volume of local disk, request it with the “–tmp” argument:
sbatch -n 2 -t 1-0 --tmp=4096 # requests 4GB of disk space
Note that this only ensures that the disk is available when the job starts. Other processes may fill up this scratch space, causing problems with your job. The location of this local scratch space is stored in the environment variable “TMPDIR” and “SCRATCH_LOCAL- use this environment variable if you need local storage on the node- do not use “/tmp” for storage of files or for scratch space. Node local job scratch spaces are only available on gizmo nodes, not on rhino.
Network Job Scratch
Network global scratch space is a scratch directory that is created on storage that is available to all nodes in your job’s allocation. The directory is based on the job ID. You should access the job scratch directory by using the environment variable “$SCRATCH” in your shell scripts, for example use $SCRATCH/myfile.csv to write to a file. Node local job scratch spaces are only available on gizmo nodes, not on rhino.
Sometimes you need to work with temporary data that is not part of a specific pipeline, for example if you are doing manual QA on data for a few days or even weeks. The persistent scratch file system is accessible via environment variables $DELETE10, $DELETE30 and $DELETE90 and the files in these folders will be removed after 10, 30 or 90 days of inactivity. The $DELETE30 folder is currently available on Gizmo and $DELETE10 folders are currently avialble on Beagle and Koshu. These folders can also be reached from other operating systems: In Windows you can select (x:\scratch\delete30 ) and on Mac you select smb://center.fhcrc.org/fh/scratch/delete30.
How long will my data stay in persistent scratch?
In $DELETE30 the data will stay on the file system for 30 days after you have stopped accessing it. 3 days before the data is deleted you (the owner of the files created) will receive an email with a final warning:
From: firstname.lastname@example.org [mailto:email@example.com] Sent: Tuesday, August 23, 2016 11:32 PM To: Doe, Jane <firstname.lastname@example.org> Subject: WARNING: In 3 days will delete files in /fh/scratch/delete30! This is a notification message from fs-cleaner.py, Please review the following message: Please see attached list of files! The files listed in the attached text file will be deleted in 3 days when they will not have been touched for 30 days: # of files: 247, total space: 807 GB You can prevent deletion of these files by using the command 'touch -a filename' on each file. This will reset the access time of the file to the current date.
As an alternative to the environment variable $DELETE30 you can also reach scratch through the file system at
/fh/scratch/delete30, however the file system may be subject to change whereas the environment variable will be supported forever.
How can I use Scratch?
In jobs on
Gizmo, environment variables can be used to write and then read temporary files, e.g. $SCRATCH/myfile.csv, $SCRATCH_LOC/myfile.csv or $DELETE30/lastname_f/myfile.csv ($DELETE10 and $DELETE90 are in preparation). Similarly, jobs on Beagle can currently use $SCRATCH/myfile.csv and $DELETE10/lastname_f/myfile.csv.
The files under $SCRATCH_LOC and $SCRATCH are automatically deleted when your Gizmo or Beagle job ends. You can also reach Scratch storage space via Windows (via the X: drive) or Mac, e.g. smb://center.fhcrc.org/fh/scratch.
Note: lastname_f stands for the last name and the first initial of your PI. If you do not see the folder of your PI please ask
Helpdeskto create it for you.
In your Bash Shell:
#! /bin/bash echo -e $TMPDIR echo -e "Network Job Scratch: $SCRATCH" echo -e "Node Local Job Scratch: $SCRATCH_LOCAL" echo -e "Node Local Job Scratch: $TMPDIR" echo -e "Persistent Scratch: $DELETE30" runprog.R > $DELETE30/lastname_f/datafile.dat
#! /usr/bin/env python3 import os print("Network Job Scratch: %s" % (os.environ['SCRATCH'])) print("Node Local Job Scratch: %s" % (os.environ['SCRATCH_LOCAL'])) print("Node Local Job Scratch: %s" % (os.environ['TMPDIR'])) print("Persistent Scratch: %s" % (os.environ['DELETE30'])) MYSCRATCH = os.getenv('DELETE30', '.') myfile = os.path.join(MYSCRATCH,'lastname_f','datafile.dat') with open(myfile, 'w') as f: f.write('line in file')
#! /usr/bin/env Rscript MYSCRATCH <- Sys.getenv('DELETE30') MYSCRATCH[is.na(MYSCRATCH)] <- '.' save('line in file', file=paste0(MYSCRATCH,'/lastname_f/datafile.dat'))
Using Scratch Temporary Storage with AWS S3 buckets and rhino
scratch storage for intermediate files during a process can be a useful way to keep storage costs low, while also using our local HPC resources (
gizmo). This adjusted way to work can be useful in reducing the tendency to store large and/or temporary data sets in
Fast storage. Due to the backup frequencies and speed configuration of
fast, any files saved here even temporarily, will be retained in the backup for quite some time.
Economy Cloud storage (AWS S3) can be a more affordable way to store large data sets, and when combined with
scratch can allow all of your current processes to work without a substantial shift in your approach.
Connect to rhino
Find Scratch space
Head over to some
Scratch space for your PI.
cd /fh/scratch/delete10/lastname_f/ mkdir workingdir cd workingdir
Copy files from S3 to Scratch
Sync the prefix(es) of the file(s) in S3 containing the data you want, down to
Note: See the AWS CLI help for using S3 commands.
aws s3 sync s3://yourbucket/yourDirectory/ .
Perform your process
Process the data however you typically do. In this example we are concatenating fastq’s from paired sequencing and then converting those into uBAMS for downstream analysis with GATK tools.
Here you can see we use the
sbatch command to send the task to
gizmo. See more about HPC Job Management and commands here.
sbatch --wrap="zcat *_R1_*.fastq.gz > forwardReads_R1.fastq" sbatch --wrap="zcat *_R2_*.fastq.gz > reverseReads_R2.fastq"
Or, you can write a quick shell script to do a process. Then you’re ready to convert from FASTQ to uBAM via a teeny shell script (miniScript.sh). You can find more about how to use Slurm and see some curated examples of approaching job management in our slurm-examples GitHub repository.
#!/bin/bash set -e module load picard/2.18.1-Java-1.8.0_121 java -Xmx8G -jar picard.jar FastqToSam \ FASTQ=forwardReads_R1.fastq \ #first read file of pair FASTQ2=reverseReads_R2.fastq \ #second read file of pair OUTPUT=forprocessing.bam \ READ_GROUP_NAME=H0164.2 \ #required; changed from default of A SAMPLE_NAME=NA12878 \ #required LIBRARY_NAME=Solexa-272222 \ #required PLATFORM=illumina \ #recommended
Execute the process.
chmod +x /fh/path/miniScript.sh sbatch /fh/path/miniScript.sh
Copy Results Back to S3
After you have performed your intended process and removed any intermediate files that are not the end result you are after and do not need to save, you can then sync the directory back up to S3. By using
sync, all of your output files and logs will go to S3 in a mirrored structure to that in
scratch. Another option is to directly sync only the files you want to save by name.
aws s3 sync workingdir/ s3://yourbucket/yourDirectory/
Be Polite: Clean up after yourself
Scratch, by definition isn’t backed up, and has a finite total size for all the users at the Hutch (the sum of all data stored in individual PI’s
scratch space is fixed). Thus, it is best when you finish work and have some output files you want to save, to sync them with S3 and then delete all of what is in
scratch. Yes, you don’t HAVE to do this as eventually your files will be deleted, but it is good practice to minimize your impact on others, AND make sure that you get in the habit of taking what you need right away.
rm -rf workingdir